2.5.0 • Published 9 years ago

process-reporter v2.5.0

Weekly downloads
3
License
MIT
Repository
-
Last release
9 years ago

process-reporter

Reports information about your node process to statsd. Use it like this:

var ProcessReporter = require('process-reporter');

var processReporter = ProcessReporter({
    statsd: statsdClient
});

processReporter.bootstrap();

It currently reports these stats:

  • yourapp.process-reporter.handles number of libuv handles
  • yourapp.process-reporter.requests number of libuv requests
  • yourapp.process-reporter.memory-usage.rss resident set size of procss
  • yourapp.process-reporter.memory-usage.heap-total total size of v8 heap
  • yourapp.process-reporter.memory-usage.heap-used amt of v8 heap used
  • yourapp.process-reporter.lag-sampler event loop lag
  • yourapp.process-reporter.gc.{gc-type}.pause-ms length of GC pauses
  • yourapp.process-reporter.gc.{gc-type}.heap-used +/- amount of bytes GCd
  • yourapp.process-reporter.gc.{gc-type}.heap-total +/- changes in heap total

To destroy the reporter just call processReporter.destroy();

Docs

The ProcessReporter constructor takes an options dictionary:

  • options.statsd, a per-worker statsd to write per-worker stats to
  • options.clusterStatsd, a cluster-wide statsd to write cluster-wide stats to

You can pass in an optional clusterStatsd that will be used to emit lag-sampler and gc.{gc-type}.pause-ms stats that are cluster wide so that your statsd aggregation can calculate more accurate P99s

2.5.0

9 years ago

2.4.0

9 years ago

2.3.0

9 years ago

2.2.0

9 years ago

2.1.2

9 years ago

2.1.1

9 years ago

2.1.0

10 years ago

2.0.1

10 years ago

2.0.0

10 years ago

1.1.3

10 years ago

1.1.2

10 years ago

1.1.1

10 years ago

1.1.0

10 years ago

1.0.0

10 years ago