-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
plugin statsd does not allow field #1876
Comments
It appears that the python client that I am using could format the udp request in a different way that I originally written.
but I can not see how I can send field to be indexed as well. I can reproduce the error I see before just doing
the first field value is ignore and test is included in the tags |
the statsd protocol is separate from influx line-protocol. Only a single "field" is supported. see https://github.com/influxdata/telegraf/tree/master/plugins/inputs/statsd |
@sparrc |
no, sorry, I will remove that |
Bug report
telegraf statsd plugin behave strangely with fields of the line protocol
[key+tags] [fields] [timestamp]
System info:
Telegraf - version 1.0.1
Steps to reproduce:
I am using python (note the space between [key+tags] [fields])
Expected behavior:
key = example.timing7
tags = service=payroll,region=us-west
fields = value=22,test=666
Actual behavior:
key = example.timing7
tags = service=payroll,region=us-west,
Additional info:
it looks like "test" in considered as a tag and "value" is completely ignored
I tried with another label then "value" to see if the term "value" was the problem but it is not.
Feature Request
I could see that the statsd plugin was announcing the field line protocol implementation since 3 Nov 2015, Do you have any plan to add it?
Use case: [Why is this important (helps with prioritizing requests)]
Statsd is used by a lot of companies. I think the adoption of telegraf (and influxdb) depend on plugins such as statsd. I think telegraf is a huge step forward to promote the adoption of influxdb already (compared to graphite). But I feel frustrated by the way statsd plugin behave. Maybe I am doing something wrong.
The text was updated successfully, but these errors were encountered: