Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

additionalVulnerabilityReportFields is not working as expected. #2242

Open
vijay2910 opened this issue Aug 28, 2024 · 1 comment
Open

additionalVulnerabilityReportFields is not working as expected. #2242

vijay2910 opened this issue Aug 28, 2024 · 1 comment
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@vijay2910
Copy link

What steps did you take and what happened:
I would like to extract additional fields like 'Description' and 'Title' from Trivy Operator reports or Prometheus metrics. I followed the documentation, added the extra fields in the values.yaml file, and then deployed the operator.
In values.yaml, I have made additions to this key "additionalVulnerabilityReportFields"
additionalVulnerabilityReportFields: "Description,Links,CVSS,Targets"

What did you expect to happen:
I'm expecting trivy to show the additional fields which are added in values.yaml. Those should be available as labels in prometheus metrics.

Environment:

  • Trivy-Operator version (use trivy-operator version): 0.24.0
  • Kubernetes version (use kubectl version): 1.30
@vijay2910 vijay2910 added the kind/bug Categorizes issue or PR as related to a bug. label Aug 28, 2024
@zapocalypse
Copy link

Not sure if you fixed this already, but I set the metricsVulnIdEnabled under the operator setting to true:

operator:
metricsVulnIdEnabled: "true"

I didn't use the additionalVulnerabilityReportFields, because it did not work for some reason.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

No branches or pull requests

2 participants