New vulnerability and alert derived metrics in Compass

[#1]

About derived metrics

Derived metric values are automatically calculated based on the events received for your Compass component. For example, the Deployment Frequency metric is derived from deployment events. As you ingest deployment events on your component, you'll see the metric automatically recalculate.

Compass has supported several predefined metrics derived from Builds, Deployments, and Incident events.

Metric name	Derived from
Build success rate	Build events
Build time	Build events
Deployment frequency	Deployment events
Deployment time	Deployment events
Mean time to resolve	Incident events
Recent incidents	Incident events

Build and deployment can be populated by apps like the Bitbucket, GitHub, and GitLab for Compass app, and incident events can come from JSM or the PagerDuty app.

What’s new

We recently added four new predefined metrics derived from Alert and Vulnerability events (a new event type!):

Metric name	Derived from
Critical alerts	Alert events
Non-critical alerts	Alert events
Mean time to remediate critical severity vulnerabilities	Vulnerability events
Mean time to remediate high severity vulnerabilities	Vulnerability events
Open critical security vulnerabilities	Vulnerability events
Open high severity vulnerabilities	Vulnerability events

The addition of the alert-derived metrics aligns with the recent introduction of Operations in Compass. If you use Operations in Compass, these metrics will be calculated automatically.

The vulnerability-derived metrics are a result of the new Vulnerability type, currently populated by the Snyk app.

You can always populate events using the Compass API, which you can read more about here: https://developer.atlassian.com/cloud/compass/components/send-events-using-rest-api/

We hope you find these new events and derived metrics useful!