Notifications for Insights is are enabled for Gitlab Deployment Frequency KPI.
How it works :
The average deployment frequency is calculated based on a given time date range, and the number of deployments that has happened have occurred within that time date range. Users can apply Apply strategic criteria as a part of within the KPI settingsSettings, 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:
Info |
---|
Before enabling notifications, here are some prerequisites to follow:
|
Once the GitLab Deployment Frequency KPI is has been added to the Dashboard, go to click the gear icon to configure KPI Settings.
...
Apply the appropriate tags Provide any Tags created as a part of the prerequisite #2, and the deployment stageselect a Deployment Stage from the drop-down.
Choose Provide a date range. Click Save, and once done, move to the next tab ‘Data Point Settings’ Date Range. To apply Settings, click Save.
Navigate to the Data Point Settings tab to configure.
...
Based on requirement, apply a strategic criteria Strategic Criteria for success, warning and/or failure cases, and Save.
Move Navigate to the Dashboard Notifications tab.
...
Select the tool to which the notifications should be sent to. And fill in the necessary channel detailsplatform 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 the settings to the KPI has KPI Settings have been applied , every time and a new pipeline runs, the platform will calculate the deployment frequency for the selected provided filters and date range, and . This will send a notification if either of the threshold has thresholds have been breached.
Example
...
Screenshot of
...
Notifications
...