-
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
Consul input with prometheus output on new versions #5880
Comments
You might need 1.10.3 or later which include #5680. But based on the error I'm not so sure this is fixed, if 1.10.3 still has errors could you run this command and add the output:
|
Hello @danielnelson, My report was for version 1.10.4, so I compared all versions mentionned in this topic. extract from 1.9.0 :
It works, no errors on prometheus, and metrics are present on the /metrics output. extract from 1.10.3 :
extract from 1.10.4 :
Best regards |
Hello, For now, I decided not to put consul input in production because the latest procstat is simply awesome on 1.10.x. I'll retry consul_exporter later, but I am available to test anything you need on consul input. Best regards, Charles, OSD42 |
Hello,
output : Have a good day ! |
Relevant telegraf.conf:
System info:
centos 7.6 (linux 64)
telegraf 1.9.0 OK
telegraf 1.10.4 KO
Steps to reproduce:
log output :
Expected behavior:
Consul Health Checks are recorded by the prometheus scraping
Actual behavior:
No metrics are stored by prometheus because the prometheus output (/metrics) does not mention consul plugin inputs.
There are closed issues on the same theme with empty tags which were corrected in telegraf 1.10.2 but I still have the same issue.
I tried to tagexclude as described in issue #5522 but I don't really understand the pattern : "Serf SerfHealth ^external ", or with the tag name. But I still have the same issue with telegraf 1.10.4.
For the while I downgraded to 1.9.0 with no output error and prometheus recording metrics.
See also #2422 with older version but reopened.
The text was updated successfully, but these errors were encountered: