Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Notifications for Insights is enabled for Gitlab Deployment Frequency KPI.

How it works :

The average deployment frequency is calculated based on a given time range, and the number of deployments that has happened within that time range. Users can apply strategic criteria as a part of the KPI settings, where they define the success and failure goals. Strategic Criteria, Tags, Deployment Stage, and Date filter are what will contribute to the trigger of a notification.

How to set it up :

Before enabling notifications, here are some prerequisites to follow:

  1. Create Tags

  2. Create Project Mappings

  3. Create a New Dashboard

  4. Add Gitlab Deployment Frequency KPI to the Dashboard : How To: Add KPIs to a Dashboard

Once Deployment Frequency KPI is added to the Dashboard, go to Settings.

Apply the appropriate tags created as a part of the prerequisite #2, and the deployment stage.

Choose a date range. Click Save, and once done, move to the next tab ‘Data Point Settings’.

Based on requirement, apply a strategic criteria for success, warning and/or failure cases, and Save.

Move to the Dashboard Notifications tab.

Select the tool to which the notifications should be sent to. And fill in the necessary channel details.

Once completed, click Save and Close.

How to View Notifications :

Once the settings to the KPI has been applied, every time a new pipeline runs, platform will calculate the deployment frequency for the selected filters and date range, and will send a notification if either of the threshold has been breached.

Example screen of notifications:

  • No labels