Alert if scraping jobs fail #590
Merged
+24
−60
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
In addition to alerting on failing scraping jobs, we need to address our existing failures, which I researched in NixOS#551. Copy pasting analysis from there: - `r13y`: Last successful scrape: 2024-09-21. Website is down. @grahamc didn't respond to my query. - `rfc39`: IMO, this is mis-architected. This scrapes a job that only runs periodically, which means we regularly get scrape failures. I've filed NixOS/rfc39#14 with the upstream project seeking advice. - Since we don't actually alert on these metrics, I propose doing the simplest thing and just disabling this scrape job for now. - `hydra_notify`: Last successful scrape: 2024-08-02. We disabled this service [in 2024](NixOS@66da5cf), there's no reason to keep scraping it.
|
applied |
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.
In addition to alerting on failing scraping jobs, we need to address our existing failures, which I researched in
#551. Copy pasting analysis from there:
r13y: Last successful scrape: 2024-09-21. Website is down. @grahamc didn't respond to my query.rfc39: IMO, this is mis-architected. This scrapes a job that only runs periodically, which means we regularly get scrape failures. I've filed Recommendations for integrating with Prometheus? rfc39#14 with the upstream project seeking advice.hydra_notify: Last successful scrape: 2024-08-02. We disabled this service in 2024, there's no reason to keep scraping it.(fixes #551)