Fix for gaps in prometheus metrics. #6
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Instead of single crons.prom file, now each job will have it's own. However, by default node_exporter' textfile don't merge them and use only first one. Details in prometheus/node_exporter#1885 Updates: * instead of single crons.prom file, each job now have - and locks - it's own * added same HELP header to all files * cron_job metric renamed to cronjob * minor README updates
|
Wait with merging, it still have gaps |
|
Updated version looks ok, no gaps with multiple metrics. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I had gaps in prometheus metrics for few minutes.
Problem occurs with 5 cron jobs - because of locked crons.prom file.
Details in commit description.