-
Notifications
You must be signed in to change notification settings - Fork 94
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
fix: resolve enabling NodeMonitoring breaks target status
After NodeMonitoring was added, when it is configured, target status stops working completely. Long story short, the problem is early exit on an unknown scrape pool format. This change includes some refactoring originally part of the ProbeMonitoring PR (#766) but also adds in the possibility of supporting a NodeMonitoring target status if we choose to add it in the future, by at the very least detecting and validating the scrape pool format. Changes include: - Ensures we still patch everything on error (with new unit test case). - Show all errors, not just the last one we found. - Ensures we parse NodeMonitoring scrape pool formats (with new unit test case). - Validate expected errors in the test cases. Thanks @bwplotka for finding this issue!
- Loading branch information
1 parent
e547f5b
commit a2df2c4
Showing
3 changed files
with
254 additions
and
79 deletions.
There are no files selected for viewing
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
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
Oops, something went wrong.