-
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
Prometheus Input: Metrics Dropped from Outputs When Overlapping Name Exists #7705
Comments
It looks to me like
|
I had forgotten to add that this occurred after the switch to metric_version 2. When inputs and outputs were metric_version 1, we did not see this issue. That being said, if what you're saying is true, then I suppose this could be an issue with micrometer. I'm not sure I understand why this is requiring quantiles to rewrite and output metrics to prometheus, regardless of type. Could you explain the reasoning why it behaves this way? |
I've run telegraf with debug enabled to attempt to get more information on this.
|
I don't remember why I disallowed it originally but it doesn't seem to be a requirement that a SUMMARY have any quantile entries, so I'll remove the restriction (#7740). |
Relevant telegraf.conf:
System info:
Telegraf version: 1.14.4
Operating System: Linux {hostname} 4.15.0-52-generic #56-Ubuntu SMP Tue Jun 4 22:49:08 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
Micrometer version: 1.4.1
Steps to reproduce:
Expected behavior:
I expect that all metrics pulled from the inputs to be available at the prometheus output endpoint.
Actual behavior:
Metrics are ignored when measurement name overlaps.
Additional info:
curl http://localhost:8203/{appname}/manage/prometheus | grep http_
curl http://localhost:9126/metrics | grep http_
The text was updated successfully, but these errors were encountered: