← All insightsObservability

Monitoring and observability for Trivy

Nir Geier, CodeWizard · 21 March 2026 · 3 min read · Intermediate

You cannot operate what you cannot see. Here is how to get useful signals out of Trivy and turn them into alerts that mean something.

Trivy is an open-source security scanner that finds CVEs, misconfigurations, secrets and license issues across container images, filesystems, Git repos, IaC and live Kubernetes clusters.

What to watch

  • Gate on HIGH/CRITICAL with ignore-unfixed, then tighten over time
  • Scan images, IaC and filesystems - not just one surface
  • Cache and periodically refresh the DB in CI
  • Track error rate and latency, not just up/down
  • Alert on symptoms tied to user impact

Operate and inspect

bash
trivy image ghcr.io/acme/web:1.0
trivy fs --scanners vuln,secret,misconfig .
trivy k8s --report summary cluster

Keep it healthy

  • Add Trivy as a required check on pull requests
  • Generate SBOMs (CycloneDX/SPDX) for supply-chain visibility

Want senior help putting Trivy to work - or a team bootcamp on it? CodeWizard runs Israel's largest DevOps community and embeds named senior engineers with a transparent hours log. Book a free consult or explore the Academy.

Like where this is going?

Get hands-on help from the engineers who write these posts.

Book a free consult