proginoskes: Monitor the logs of one or more remote servers

Recommend this page to a friend!
  Info   View files Documentation   View files View files (7)   DownloadInstall with Composer Download .zip   Reputation   Support forum   Blog    
Last Updated Ratings Unique User Downloads Download Rankings
2018-03-05 (17 days ago) RSS 2.0 feedNot yet rated by the usersTotal: 78 This week: 2All time: 446 This week: 3Up
Version License JavaScript version Categories
proginoskes 1.0.1MIT/X Consortium ...1.0Networking, Node.js, Files and Folders
Description Author

This Node.js package can monitor the logs of one or more remote servers.

It can connect to one or more given remote servers via SSH and capture the changes in given log files using the tail command.

The remote servers can be connected via SSH using given user names and passwords or private keys.

Innovation Award
JavaScript Programming Innovation award nominee
February 2015
Number 3
In networks with many servers, usually it is necessary to keep track of relevant activity in all servers.

This Node.js module can help monitoring the activity of several servers in a central place by keeping connections to all servers at the same time and capturing the output of relevant log files being updated on those servers.

Manuel Lemos
  Performance   Level  
Name: Jason Gerfen <contact>
Classes: 7 packages by
Country: United States United States
Age: 42
All time rank: 122 in United States United States
Week rank: 6 Up1 in United States United States Up
Innovation award
Innovation award
Nominee: 4x

Winner: 2x



Monitor your infrastructure in real time using ssh to centralize a stream of log events

a drove of dragons


To install npm install proginoskes


The available configuration sections and options.

  1. global: Anything defined here is applied to all defined hosts 1. host: A host name defined here will work as a defined host 2. port: The default is 22 and is applied to all hosts unless explicitly defined 3. username: A username defined here will apply to all hosts 4. password: A password defined here will also apply to all hosts 5. privateKey: The path to a private ssh key (also applies to all defined hosts) 6. logs: An array of logs to monitor for all defined hosts
  2. hosts: The recommended method of including host definitions 1. host: The name or IP of machine to apply log monitoring streams 2. port: The SSH port for this particular host, uses global port option if omitted 3. username: The username for access, also uses the global username option if omitted 4. password: The password for access, again, uses the global password option if omitted 5. privateKey: The path to an SSH private key to use with this host. Will also use anything defined in global privateKey if omitted 6. logs: An array of logs to monitor for this host. Adds to anything defined in global logs array


var options = {
  global: {
    port: 22, //all hosts use this port unless defined
    username: 'root', //all hosts use this account unless defined
    privateKey: './path/to/global/privatekey', //all hosts use this key unless defined
    logs: [
      '/var/log/ufw.log' //all hosts stream these logs
  hosts: [
      host: 'host-1.example',
      privateKey: './path/to/host-1.example/privatekey',
      logs: [
      host: 'host-2.example',
      port: 2222,
      username: 'iamroot',
      privateKey: './path/to/host-2.example/privatekey',
      host: 'host-3.example',
      password: 'secret-sauce',
      logs: [


Once you have a good configuration with at least one defined host to monitor usage is easy.


var cherubum = require('proginoskes');

cherubum.proginoskes(options, function(err, data) {
  if (err) throw err;


returned object

The returned object(s) are simple, but makes it easy to determine source.


[ { server: 'server-1',
    log: '/var/log/ufw.log',
    data: 'Jan  9 07:24:12 node kernel: [UFW BLOCK] IN=eth0 OUT= MAC=52:54:00:12:34:56:52:55:0a:00:02:02:08:00 SRC= DST= LEN=44 TOS=0x00 PREC=0x00 TTL=64 ID=1593 PROTO=TCP SPT=60948 DPT=443 WINDOW=8760 RES=0x00 SYN URGP=0' },
  { server: 'server-2',
    log: 'access-logs/some-site.com',
    data: 'xxx.xxx.xxx.xxx - - [09/Jan/2015:08:23:13 -0600] "POST /wp-cron.php?doing_wp_cron=1420813393.8197140693664550781250 HTTP/1.0" 200 - "-" "WordPress/4.0.1; http://some-site.com"' } ]
  Files folder image Files  
File Role Description
Files folder imagelib (1 file)
Files folder imagetest (1 file)
Accessible without login Plain text file index.js Appl. Application script
Accessible without login Plain text file LICENSE Lic. License file
Accessible without login Plain text file Makefile Data Auxiliary data
Accessible without login Plain text file package.json Data Auxiliary data
Accessible without login Plain text file README.md Doc. Documentation

  Files folder image Files  /  lib  
File Role Description
  Plain text file proginoskes.js Class Class source

  Files folder image Files  /  test  
File Role Description
  Accessible without login Plain text file index.js Example Example script

 Version Control Unique User Downloads Download Rankings  
This week:2
All time:446
This week:3Up