Loss of Metrics (vuln metrics) #2737
Unanswered
lesaugues
asked this question in
Help & Support
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello, I’ve been using Trivy Operator on my Kubernetes cluster for quite some time to continuously scan for vulnerabilities in my images.
I use the metrics emitted by the operator to collect information and set up alerts afterward.
I’ve set a TTL of 24h on my vulnerability reports so that they expire, making sure I don’t miss any potential new vulnerabilities that might appear.
However, I don’t fully understand the lifecycle of my reports. When a report expires (due to my TTL), I end up with a gap in my metrics for a while (several hours). This causes multiple issues, especially with alerting (false positives).
Is there a way to ensure that when a report expires (because of TTL) the operator automatically triggers a new job to generate a fresh report (so that there’s always a vulnerability report per resource)?
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions