ROX-28151: Tracker runner, triggered by Prometheus scrape request#15797
ROX-28151: Tracker runner, triggered by Prometheus scrape request#15797parametalol merged 18 commits intomasterfrom
Conversation
|
Skipping CI for Draft Pull Request. |
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## master #15797 +/- ##
==========================================
+ Coverage 48.62% 48.68% +0.05%
==========================================
Files 2664 2674 +10
Lines 199336 199708 +372
==========================================
+ Hits 96932 97219 +287
- Misses 94809 94882 +73
- Partials 7595 7607 +12
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
013331f to
e7f93c7
Compare
4cf2b93 to
25e1bb8
Compare
e7f93c7 to
a76cb2a
Compare
|
Images are ready for the commit at 924e8b3. To use with deploy scripts, first |
60b7302 to
17d90da
Compare
a76cb2a to
a7eaed4
Compare
17d90da to
64d7b55
Compare
a7eaed4 to
b2392c1
Compare
9430e5c to
fe18a4b
Compare
a8c335e to
a719ed0
Compare
232068a to
96cfe28
Compare
11b8374 to
7dba6d0
Compare
96cfe28 to
38551df
Compare
There was a problem hiding this comment.
I like the idea of using the Prometheus registry as a cache that is invalidated upon user request. What is not clear to me is how stale labels get purged from the cache? IIUC stale findings from previous gathers remain as metrics in the registry - is that right? Ideally these stale findings would be purged after the gathering period expired.
CHANGELOG.md
7058c8a to
924e8b3
Compare
|
@parametalol: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
Description
Custom Prometheus metrics exposed on the
/metricspath of the central API endpoint. Configured via the/v1/configservice.This PR adds the image vulnerabilities tracker and sets it up on a dedicated route, and enables configuration via the config service API.
Disabled by default.
User-facing documentation
Testing and quality
Automated testing
How I validated my change
CI
Current dependencies on/for this PR: