-
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
Type loss and metric rename in prometheus input → prometheus output #2950
Comments
Can confirm this issue. Any metrics that traverse through telegraf are losing their metric types. We also have Prometheus as the input and output. |
I can confirm this is present in 1.4.1. I think the offending line is found here
|
After thinking about this a little further, I think this would have to be addressed on the input and not the output. Trying to address this on the output would be difficult, as histogram types would have to construct new histogram labels and use the field names as the label value. For any other single value metric, the field name should get used as the type. |
Will this be added to the 1.5 milestone? |
This is mostly addressed by #3337. Types are still lost, but metric names are no longer mangled unnecessarily. |
Bug report
Loading the data with telegraf Prometheus input and exporting it with the prometheus output (e.g. haproxy-exporter --[prometheus protocol]--telegraf---[prometheus protocol]---…) yields
*_<type>
(e.g.haproxy_up
becomeshaproxy_up_gauge
)untyped
Relevant telegraf.conf:
System info:
Tested in
Steps to reproduce:
prometheus_client
Expected behavior:
Actual behavior:
*_<type>
(e.g.haproxy_up
becomeshaproxy_up_gauge
)untyped
haproxy exporter gives:
Telegraf exports:
The text was updated successfully, but these errors were encountered: