Notifications
Last updated
Was this helpful?
v0.7
Last updated
Was this helpful?
Monitoring updates of your CI/CD pipelines, such as their triggers, successes, and failures, can be challenging without a proper notification system in place.
The Notifications module in Devtron helps you solve this problem by sending you timely updates about your CI/CD pipelines through various mediums such as Email, Slack, Discord, and much more - ensuring you stay informed at all times.
Notifications module integration installed in your Devtron instance.
For Enterprise users: This module comes installed by default.
The Notifications page allows you to configure and manage notifications for your CI/CD pipeline(s). To access the Notifications page, navigate to Global Configurations → Notifications.
The Notifications page has the following two tabs:
Configurations - Allows you to configure the way (Email SES, Email SMTP, Slack, Webhook) through which the notifications will be delivered.
Notifications - Allows you to define the recipients and the events (e.g., CI/CD success, failure, trigger) for which the notifications must be sent out.
You can configure notifications in Devtron in the following four ways:
AWS access key and secret key - When obtaining access key and secret access key from AWS SES, make sure to generate them from the Security credentials page (Profile → Security credentials → Access keys → Create access key).
Navigate to the Global Configurations → Notifications → Configurations → Email (SES) → Add SES.
Enter the following details in the Configure SES page:
Configuration Name
Give a name to your SES Configuration, e.g., qa-ses
Access Key ID
Valid access key from your AWS Security credentials page, e.g., AKIAWEAVHF123ABCD123
Secret Access Key
Secret access key from your AWS Security credentials page
AWS Region
The AWS region you used while setting up SES, e.g., United States (Ohio)
Send email from
The sender email address verified by SES for sending emails
Enable the Set as default configuration to send emails check box (optional) if you wish to keep this configuration as the default one for sending emails.
Click Save.
Navigate to the Global Configurations → Notifications → Configurations → Email (SMTP) → Add SMTP.
Enter the following details in the Configure SMTP page:
Configuration Name
Give a name to your SMTP Configuration, e.g., qa-smtp
SMTP Port
The port number available in your SMTP settings, e.g., 587
SMTP Host address/Server
The SMTP endpoint available in your SMTP settings, e.g., smtp.gmail.com
SMTP Username
A valid username created with your SMTP provider, e.g., AKIAWEAVHF123ABCD123 in case of AWS SMTP and johndoe@gmail.com in case of Gmail SMTP.
SMTP Password
The password generated by your SMTP provider
Send email from
The sender email address verified by your SMTP provider for sending emails
Enable the Set as default configuration to send emails check box (optional) if you wish to keep this configuration as the default one for sending emails.
Click Save.
Navigate to the Global Configurations → Notifications → Configurations → Slack → Add Slack.
Enter the following details in the Configure Slack page:
Slack Channel
Name of the Slack channel on which you wish to receive notifications, e.g., qa-slack-channel
Webhook URL
Enter a valid incoming webhook URL
Project
Select the project name to control user access. Apps outside your selected project cannot use this configuration, e.g., qa-demo
Click Save.
A Webhook URL to receive notifications (e.g., Microsoft Teams Webhook URL, Discord Webhook URL).
Navigate to the Global Configurations → Notifications → Configurations → Webhook → Add Webhook.
Enter the following details in the Configure Webhook page:
Configuration name
Give a name to your webhook configuration, e.g., qa-webhook
Webhook URL
Enter a valid Webhook URL link
Headers
Add optional key-value pairs, e.g. Content-Type: application/json
Data to be shared through webhook
Write the payload content of the notification in a JSON format. Refer:
Click Save.
Once you have configured the notifications in the Configuration tab, you can then add, edit, and delete notifications in the Notifications tab. To create a new notification, follow the below instructions:
Navigate back to the Notifications tab.
Click the Add Notification button. The Add Notifications page is displayed.
Enter your preferred recipient in the Send to drop-down box. You can add one or more recipients in the Send to drop-down box and the recipients can be any or all of the following:
a. A verified email address (by SES/SMTP)
b. A Slack channel
c. A Webhook
Select your preferred filter type from the following in the Select pipelines field:
a. Application - Select Application, if you specifically know for which application(s) you need notifications for.
b. Project - Select Project, if you want notifications for one or more applications within specific project(s).
c. Environment - Select Environment, if you want notifications for applications deployed in specific environment(s) (e.g., production).
d. Cluster - Select Cluster, if you want notifications for applications in a specific cluster(s).
Once you have selected your preferred filter type, a list of CI/CD pipelines are displayed as filter results.
You can also choose to receive notifications for any CI or CD pipelines that do not exist currently but may exist in future by enabling the All current and future pipelines matching pipeline in the Pipeline Name column.
Select your preferred events for which a notification must be sent out in the Events column. The labels are displayed when you hover over the check boxes. You can enable one or more events as per your requirements.
a. Trigger - Enable this if you wish to receive notification whenever the pipeline is triggered.
b. Success - Enable this if you wish to receive notification upon a successful build or deploy.
c. Failure - Enable this if you wish to receive notification upon a failed build or deploy.
Click Save. The notification is now successfully added. You can now build and deploy your application to get notifications of its CI/CD events.
You can always edit existing notifications instead of deleting them and creating new ones from scratch. For example, if you initially created notifications for Trigger and Failure events of your CI/CD pipelines, you can perform removal/addition of events anytime by modifying them.
To modify the events, follow the below steps:
Navigate to the Notifications tab.
Select your preferred notification.
Check the check box in the left side of the notification to select it.
Click Modify Events to modify the events. Check or uncheck the events based on your requirements.
Click Apply.
When creating notifications, if you previously added a recipient but now no longer want them to receive the CI/CD notifications, or if you want to add a new recipient or remove a specific communication medium (e.g., Slack), you can do so by modifying the recipients.
To modify the recipients, follow the below steps:
Navigate to the Notifications tab.
Select your preferred notification.
Check the check box in the left side of the notification to select it.
Click Modify Recipients to modify the recipients. Add or remove the recipients based on your requirements.
Click Save Changes.
If you no longer wish to receive CI/CD notifications for an application, you can delete the corresponding notification from the Notifications tab.
If you are currently receiving CI/CD notifications for a specific application, deleting its associated notification(s) in Devtron will stop the notifications for all events and recipients mentioned in those deleted notification(s).
To delete a notification, follow the below steps:
Navigate to the Notifications tab.
Select your preferred notification.
Check the check box in the left side of the notification to select it.
Click Delete to delete the notification.
integration installed in your Devtron instance.
For OSS users: The Notifications page won't appear in Global Configurations unless you install the Notifications module from (Average installation time: ~ 5–6 minutes).
Only can create and manage SES configurations.
Verified domain/email identities on AWS SES - To know more, visit .
Now that the Email (SES) configuration is set up, you can proceed to .
Only can create and manage SMTP configurations.
Now that the Email (SMTP) configuration is set up, you can proceed to .
Only can create and manage Slack configurations.
A Slack account, a Slack channel, and an .
Now that the Slack configuration is set up, you can proceed to .
Only can create and manage Webhook configurations.
Now that the Webhook configuration is set up, you can proceed to .
indicates that it is a CI (Build) pipeline.
indicates that it is a CD (Deployment) pipeline.
