Fix prometheous inactive alerts and print version #949
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.



Description
Fixed the counting of "inactive" alerts
Previously: only firing and pending alerts were counted from /api/v1/alerts
Fix: Added a call to /api/v1/rules to iterate through groups[].rules[] and filter those with state: inactive.
Corrected display in the badge ({{ count }}) and in the text (x inactive alerts).
Added the Prometheus version (buildinfo) on desktop only.
New query to /api/v1/status/buildinfo.
Mobile detected via window.matchMedia.
Visual UX improvement
The API status is initialized to null (instead of an empty object), which prevents the badge from flashing or alerts with a default value of 0 at startup.
For your information:
Note on Prometheus Basic Authentication
Limitation of Prometheus + Basic Auth + CORS:
When using Authorization: Basic, the browser first sends an OPTIONS request (pre-flight CORS) without an authentication header. Prometheus rejects this with a 401 without CORS headers, thus blocking the actual request.
Result: It is impossible to use the Prometheus API directly from the browser with Basic Auth.
Type of change
Checklist:
config.ymlfile