statsd-influxdb-backend
statsd-influxdb-backend copied to clipboard
Support for InfluxDB v0.9
InfluxDB 0.9 is coming soon, and rc4 has just been released which features an entirely new API and a tag system for describing metrics.
In addition to the new JSON format, the backend will need a way to define a retention policy and convert from a StatsD metric name into tag & field key value pairs.
Just hoping to start a discussion on how to approach this.
I have a pull request for the v0.9 API support, it's currently pending at https://github.com/bernd/statsd-influxdb-backend/pull/14.
PR #14 has been merged. Can you please test if this works for you? Thanks!
Just starting to read up on influx and statsd myself. Noticed this work lets statsd work with influxdb 0.9, but doesn't support tags. Is that right?
Although I'm not sure how it could work...
yeah I don't see how statsd could support tags, but I'm open for ideas!
one possible idea would to make set the tags in the config file. You already have to specify a db which means (at least in my environment) multiple statsd collectors anyway. If there was an item in the config file for tags to send along with the data when it flushes to influxdb.
version 0.9 implements new line protocol for writing instead of JSON https://github.com/influxdb/influxdb/pull/2696
Final JSON API changes have been merged with #17.
Shouldn't this ticket be closed if the support has been implemented already?
I haven't gotten to updating the code to work with the final version of the v0.9 api, hoping to get to it this week.
@imreACTmd Are you referring to the new line protocol api in v0.9?
How about parsing out tags from metric names, like InfluxDB graphite plugin can nowadays do? See https://github.com/influxdb/influxdb/blob/master/services/graphite/README.md
+1 Would love to see the support for tags
+1 need tag support !!!
Some action is happening on this
fork, but no documentation on how to utilise this yet - I'm guessing the __t__
string is being used to specify the start of a tag, but I'm not sure this edit adds support of mutl-value or multiple tags yet.