numbat-powered metrics collector & redirector


Numbat-Powered Metrics system: monitoring, alerting, and historical analysis. The collector sits in front of Numbat-Analyzer and InfluxDB in the same way that statsd sits in front of Graphite. This system, however, does absolutely no aggregation or manipulation of the data at all (yet). It merely multiplexes & buffers when necessary.

See numbat-analyzer for more information on the system.

The collector is a service. You are intended to run it anywhere you like, perhaps many instances of it. You could run one on every hosts where you run services and communicate with it using a socket. Or you could run a few collectors and communicate using TCP or UDP.

In production at npm.

> npm install -g numbat-collector
> numbatd configuration.js

The configuration file looks like this:

module.exports =
        name: 'numbat-1',
        silent: false
    listen: { host: 'localhost', port: 3333 },
        { type: 'log', name: 'numbat-1', path: './numbat.log' },
        { type: 'analyzer',  host: 'localhost', port: 5555 },
            type: 'influxdb',
                { host: '',  port: 8086 },
                { host: '',  port: 8086 },
            username: 'numbat',
            password: 'my-top-secret',
            database: 'numbat'
        { type: 'prettylog', name: 'foobar' },
        { type: 'jut', target: 'http://uri-of-collector', batchSize: 500 },
        { type: 'graphite', host: 'localhost', port: 3333 },

The configuration options are described in more detail below.

Logs JSON-formatted data to the console by default.

  • name: nodename: name to tag all log entries with
  • silent: true: no logging at all
  • NODE_ENV=dev set in environment: log to console, pretty-printed (no need to pipe to bistre)
  • listen: { host: '', port: 3333 } -- listen for incoming data over tcp on the given port
  • listen: { host: 'localhost', port: 3333, udp: true } -- listen for udp data
  • listen: { path: '/path/to/foo.sock' } -- connect to the given unix domain socket

These options are mutually exclusive.

  • influx: InfluxDB: a time-series database that can drive interesting dashboards.
  • logfile: a json-formatted logfile (using bole); in case you want logging for any reason
  • prettylog: a pretty-formatted colorized console log
  • analyzer: numbat-analyzer, the incomplete alerting & monitoring component of the numbat-powered metrics system.
  • graphite: Graphite (plain graphite, not statsd)
  • jut:

You can have as many outputs as you want.

Sure! Write tests with mocha & must. Use BSD/Allman bracing or I will stare at you funny and not take your pull request.