Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upIssue with relabelling after checkpointing is run #2391
Comments
This comment has been minimized.
This comment has been minimized.
|
Sounds like a dupe of #2377. The checkpointing is unrelated. |
brian-brazil
closed this
Feb 2, 2017
This comment has been minimized.
This comment has been minimized.
lock
bot
commented
Mar 24, 2019
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
lock
bot
locked and limited conversation to collaborators
Mar 24, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
chriswiggins commentedFeb 2, 2017
What did you do?
Configured prometheus to scrape an SNMP Exporter endpoint
What did you expect to see?
Working continuously
What did you see instead? Under which circumstances?
As soon as prometheus does the following checkpointing from the log, the target relabelling on the SNMP targets is incorrectly set. On a restart, the target is set to the SNMP device IP, however after the checkpointing the target is set to the device running the SNMP exporter
Environment
System information:
Linux 3.13.0-32-generic x86_64
Prometheus version:
127.1.2.3 is just an example IP of the exporter
Sample of what is in the JSON files:
See above section with the output.
I've tried to enable debug logging with
-log.level=debughowever this doesn't provide any more information.If you'd like me to send more detailed information without replacement of IPs etc then I'm happy to do so.
Really appreciate the help!