-
Notifications
You must be signed in to change notification settings - Fork 481
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
metrics expiry #83
Comments
This has been discussed previously, we will not be adding this feature. See #19 |
So, I was hoping I could alert on cron-based scripts used to backup stuff off my servers to a remote storage. I made each script send it's exit status to prometheus-pushgateway. It works well - I defined alert rules for a non-zero exit status. Now, how do I alert if the scripts crash in the middle (or don't run at all) and therefore dont send their exit code ? The pushgateway reports the last status forever, so I'll never know there is a problem with the script. |
P.S. I read the thread #19 Is my solution for this use case an antipattern ? Why ? What's the prometheus-based best practice approach to monitoring cron script results ? |
http://www.robustperception.io/monitoring-batch-jobs-in-python/ explains how to do this from Python. |
Ok, understood, additional metric for time of last success. Thanks @brian-brazil |
It'd be nice if there was a configuration parameter to specify how long the metric should "live" inside the pushgateway and then expie.
The text was updated successfully, but these errors were encountered: