-
Notifications
You must be signed in to change notification settings - Fork 74
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tag support #21
Comments
Another possibility: Here's a thread from the dropwizard metrics forum about what that project may do for tag support - (https://groups.google.com/forum/#!topic/metrics-user/95Dv1xcOox0) |
Hi, also, influxdb 0.9 need to use the new line protocol to pass tags (no more json), https://influxdb.com/docs/v0.9/write_protocols/write_syntax.html So, it's not too much different than opentsb |
Seem that somebody already done it in this fork :) |
here another implementation : starsy@a0c97e5 |
The second implementation has also been issued as a PR here: #22. I had meant to submit ours as a PR once we confirmed it was working for us, but the line protocol seems strictly cleaner. |
I have seen a couple different ways that statsd-to-X bridges enabled support for tagging. This project does it by looking for tags embedded as part of the metric name. It is ugly, but probably safest since it makes no assumption about how the statsD process looks at data after the type constant.
A cleaner way is how DataDog does it (see format). I have used this
fork of a popular statsd client library to push data in this way, but it may assume that the DD agent is the statsD service (rather than a generic statsD service that would barf on the data after the type data).
Just tossing ideas out. We are looking at using influxDB and need a statsD-with-tags solution. I can't offer to help (yet), but maybe someone else can get a jump on things using either of these approaches as a basis.
The text was updated successfully, but these errors were encountered: