文件列表:

lib (0, 2011-08-25)
lib\statsd-instrument.coffee (1470, 2011-08-25)
lib\statsd-instrument.js (2430, 2011-08-25)
package.json (739, 2011-08-25)
test (0, 2011-08-25)
test\spec (0, 2011-08-25)
test\spec\statsd-instrument_spec.coffee (5852, 2011-08-25)
test\spec\statsd-instrument_spec.js (6960, 2011-08-25)

# Instrumentation for the StatsD client for Node.js apps (node-statsd) ======================================================================== [Etsy Node.js StatsD](http://github.com/etsy/statsd) is a lean-and-mean server for gathering and analyzing application metrics generated by StatsD clients and then creating graphs from those metrics by dispatching them into [Graphite](graphite.wikidot.com/). This module is based on the excellent [Shopify statsd-instrument Ruby module](https://github.com/Shopify/statsd-instrument/) and it allows instrumentation of methods so that they will measure and count StatsD metrics without coupling the actual StatsD plumbing code with your logic code. As Shopify puts it - "lets you define all of your instrumentation in one file and not litter your code with instrumentation details". Unlike the Shopify module, which implements it's own Ruby StatsD client handling (UDP) communication against the StatsD server, this module only provides the instrumentation functions and relies on the existing [node-statsd module](https://github.com/sivy/node-statsd) by [sivy](https://github.com/sivy) for communicating with the Etsy StatsD server. ## Major differences from Shopify statsd-instrument for Ruby 1. No configuration - no logging, no different modes of operation (production/testing/etc). 2. Vows-based tests that demonstrate and test the usage of the instrumentation in an artificial scenario instead of rewriting Shopify tests in say, nodeunit. ## Installation % npm install node-statsd-instrument ## Usage ## Initialization ``` javascript StatsD = require('node-statsd').StatsD; StatsDInstrumentation = require('node-statsd-instrument').StatsDInstrumentation; statsd_client = new StatsD('127.0.0.1', 8125); statsd_instrument = new StatsDInstrumentation(statsd_client); ``` or you can use node-statsd StatsD client straight from this module - ``` javascript instrument = require('node-statsd-instrument'); statsd_client = new instrument.StatsD('127.0.0.1', 8125); statsd_instrument = new instrument.StatsDInstrumentation(statsd_client); ``` ### Instrumenting Object Methods If you have a method in an object you would like to instrument, do this - ``` javascript statsd_instrument.count(some_object, 'some_object_method', 'some.counter') ``` ### Instrumenting Class Methods You can instrument prototypal class-like methods just like object methods by using the metaprogramming methods. You simply need to give the 'class' prototype as the object - ``` javascript statsd_instrument.count(SomeClass.prototype, 'some_class_method', 'some.counter') ``` ## Metaprogramming Methods Use the methods provided below to instrument methods in your objects. ### count This will increment the given key even if the method doesn't finish successfully (returns false, raises).s ``` javascript statsd_instrument.count(some_object, 'some_object_method', 'some.counter') ``` ### measure This will measure the method's runtime (in milliseconds) and report it to StatsD using the StatsD timing counter (StatsD.timing from node-statsd). ``` javascript statsd_instrument.measure(some_object, 'some_object_method', 'some.timing.counter') ``` ### count\_if This will only increment the given key if the method executes successfully. ``` javascript statsd_instrument.count_if(some_object, 'some_object_method', 'some.counter') ``` So now, if some\_object.some\_object\_method raises an exception or returns false (ie. result == false), we won't increment the counter. You can pass a function to evaluate what success and failure means - ``` javascript some_controller.request.url = 'someFatResource' statsd_instrument.count_success(some_controller, 'responseReceived', some_controller.request.url+'.cached', function() { this.response.source == 'cache' } ) ``` If the response was given to the client from the cache, then the evaluating function will return true and so _someFatResource.cached_ counter will be increased. Nothing happens if the evaluating function returns false. Do note that the given function is binded to the instrumented object, which is _some\_controller_ in the above example (this allows access to _some\_controller.response.source_ from inside the function body). ### count\_success Similar to count\_if, except this will increment one key in the case of success and another key in the case of failure. ``` javascript statsd_instrument.count_success(some_object, 'some_object_method', 'some.counter') ``` If this method fails execution (raises or returns false) the failure counter will be incremented ('some.counter.failure'), otherwise it will be the success counter ('some.counter.success'). Again, you can pass a function to evaluate what success and failure means - ``` javascript some_controller.request.url = 'someFatResource' statsd_instrument.count_success(some_controller, 'responseReceived', some_controller.request.url+'.caching', function() { this.response.source == 'cache' } ) ``` If the response was given to the client from the cache, then the evaluating function will return true and this will be considered a success and so the _someFatResource.caching.success_ counter will be increased. Otherwise, the evaluating function will return false and _someFatResource.caching.failure_ will be increased, indicating that there was a failure in caching _someFatResource_. Again, do note that the given evaluating function is binded to the instrumented object (_some\_controller_).

近期下载者：

相关文件：

评论：[我要评论] [举报此文件]

收藏者：