StatsD backend for CopperEgg
$ cd /path/to/statsd $ npm install copperegg-statsd-backend
You have to add the following basic configuration information to your StatsD config file. You can find your apikey in the CopperEgg webapp, under Settings.
copperegg-statsd-backend backend to the list of StatsD
backends in the StatsD configuration file:
Start/restart the statsd daemon to pick up the changes and have your metrics sent to CopperEgg.
Additional configuration options
The CopperEgg backend also supports the following optional configuration
options under the top-level
debug: For debugging if something goes wrong.
metric_group: This is the name of the metric group you created in the CopperEgg UI. Defaults to 'statsd' but you need to create it. It should contain a metric for each metric name you send to statsd.
object_name: This is a way to identify the metrics. The default is to use the hostname of the system statsd is running on. You can change this to anything you want as long as it is unique. Metrics you send will be 'attached' to this object.
Publishing to multiple backends simultaneously
You can push metrics to multiple backends simultaneously, such as
CopperEgg and Graphite. Just include both backends in the
backends: "./backends/graphite" "copperegg-statsd-backend"...
See the statsd manpage for more information.
If you want to contribute:
- Clone your fork
- Hack away
- If you are adding new functionality, document it in the README
- Push the branch up to GitHub
- Send a pull request