Skip to content

Add metric to track when CVS cannot scan a component

Olivier Gonzalez requested to merge add_metrics_cvs_cannot_scan_component into master

What does this MR do and why?

Add internal metrics to track the following feature behavior: when Continuous Vulnerability Scanning operates, it can encounter errors which prevents it from scanning a component and determining if it is affected by a given advisory or not.

This can happen for multiple reasons and Sentry error tracking can be enabled when needed (behind OPS flag, see !165184 (merged)) to further investigate the problem.

For the purpose of this product metric, we don't distinguish these various causes and simply count all errors for now.

Refs: #481980

Changelog: other EE: true

MR acceptance checklist

Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

Before After

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

Edited by Olivier Gonzalez

Merge request reports