Node.js Agent for Instrumental Application Monitoring
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.

Instrumental Node.js Agent

Instrumental is an application monitoring platform built for developers who want a better understanding of their production software. Powerful tools, like the Instrumental Query Language, combined with an exploration-focused interface allow you to get real answers to complex questions, in real-time.

This agent supports custom metric monitoring for Node.js applications. It provides high-data reliability at high scale, without ever blocking your process or causing an exception.

Build Status


npm install instrumental-agent

Package details on


You will need to set the API token. API tokens can be found in the project tokens documentation or in your user settings page. Use the 'enabled' flag to control if the agent actually reports. This is useful for not reporting in dev/test/staging/etc. environments.


var I = require('instrumental-agent');
  // from here:
  apiKey:  'project_token',

  // optional, default shown
  host:    '',

  // optional, default shown
  enabled: true,

  // optional, default is undefined, connection timeout in ms
  timeout: 10000,


I.increment('' /*, value = 1, time = now, count = 1 */);


I.gauge('', 82.12 /*, time = now, count = 1 */);


I.notice('An event occurred' /*, time = now, duration = 0 */);

Special (dis)connection handling

If you need to control the point at which the Agent disconnects from the Instrumental metric collectors, you can manually call disconnect().

var I = require('instrumental-agent');
I.configure({ /* things */ });
/* do some work and record metrics */


Make a PR! Say roughly what you've changed, why you did so, and any ancillary data you have like gotchas, issues you suspect, awesomeness, etc.

Run the Tests and other Helpers

> npm install
> npm test # this should be all green
> npm run coverage # this should probably be like… as good as when you started
> npm run jshint # ??? I guess no errors? not sure what this does


  1. Sign up for
  2. Pull latest master
  3. Merge feature branch(es) into master
  4. npm test
  5. Increment version in repo
  • package.json
  1. Update
  2. Commit "Release version vX.Y.Z"
  3. Push to GitHub
  4. npm publish
  5. Tag version: git tag 'vX.Y.Z' && git push --tags
  6. Verify update on
  7. Refresh documentation on

Cool Contributors 😎

  • @spacetc62
  • @gmcnaught
  • @janxious
  • @jqr
  • @jason-o-matic
  • @JamesPaden
  • @pmidge
  • @acanimal
  • @alecgorge