A node.js port of Coda Hale's metrics library. In use at Yammer.
A node.js port of codahale's metrics library: https://github.com/codahale/metrics
Metrics provides an instrumentation toolkit to measure the behavior of your critical systems while they're running in production.
The MIT License (MIT) Copyright (c) 2012 Mike Ihbe
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
metrics = require'metrics';
Start a metrics Server
var metricsServer = configmetricsPort || 9091;
Servers are only one way to report your metrics. It's actually a thin layer on top of metrics.Report, which you could use to build other reporting mechanisms.
Add the metrics to the server
metricsServeraddMetric'com.co.thingA' counter;metricsServeraddMetric'com.co.thingB' hist1;metricsServeraddMetric'com.co.thingC' hist2;metricsServeraddMetric'com.co.thingD' meter;metricsServeraddMetric'com.co.thingE' timer;
Typical production deployments have multiple node processes per server. Rather than each process exposing metrics on different ports, it makes more sense to expose the metrics from the "master" process. Writing a thin wrapper around this api to perform the process communication is trivial, with a message passing setup, the client processes could look something like this:
var Metric = exports = moduleexports =thismessagePasser = messagePasser;thiseventType = eventType;thismessagePassersendMessagemethod: 'createMetric'type: typeeventType: eventType;thismessagePassersendMessagemethod: 'updateMetric'metricMethod: methodmetricArgs: argseventType: thiseventType;return thisforwardMessage'update' val;return thisforwardMessage'mark' n;return thisforwardMessage'inc' n;return thisforwardMessage'dec' n;return thisforwardMessage'clear';
And the server side that receives the createMetric and updateMetric rpcs could look something like this:
if metricsServermsgtype = msgtype0toUpperCase + msgtypesubstring1metricsServeraddMetricmsgeventType msgtype;if metricsServervar namespaces = msgeventTypesplit'.'event = namespacespopnamespace = namespacesjoin'.';var metric = metricsServertrackedMetricsnamespaceevent;metricmsgmetricMethodapplymetric msgmetricArgs;
For multiple server deployments, you have more options, but the best approach will be highly application dependent. Best of luck, and always be tracking! Using the metrics server you can hit the server on your configured port and you'll get a json representation of your metrics. You should collect these periodically to generate timeseries to monitor the longterm health of your application. The metrics.Reporting object would let you write to a log periodically or however else you'd like to expose your metrics.