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

« Previous Version 2 Current »

Notifications for Insights are enabled for Gitlab Deployment Frequency KPI. The average deployment frequency is calculated based on a given date range, and the number of deployments that have occurred within that date range. Apply strategic criteria within 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 Configure:

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 the GitLab Deployment Frequency KPI has been added to the Dashboard, click the gear icon to configure KPI Settings.

Provide any Tags created as a part of prerequisite #2 and select a Deployment Stage from the drop-down.

Provide a Date Range. To apply Settings, click Save.

Navigate to the Data Point Settings tab to configure.

Based on requirement, apply Strategic Criteria for success, warning and/or failure cases, and Save.

Navigate to the Dashboard Notifications tab.

Select the platform where notifications will be sent (Microsoft Teams, Slack or Google Chat). Enable platform toggle and provide correct tool configuration values.

Once completed, click Save and Close.

How to View Notifications:

Once KPI Settings have been applied and a new pipeline runs, the platform will calculate the deployment frequency for the provided filters and date range. This will send a notification if either of the thresholds have been breached.

Example Screenshot of Notifications

  • No labels