- Email notification using self-serve UI
- Notifications to Slack is supported using APIs
- Notifications to PagerDuty will be available soon!
From ThirdEye UI
Steps to configure a subscription group to receive email notifications is as follows:
Click on Create
Create Subscription Group
Type the “Name of the Subscription Group”
Enter schedule in cron job style (
cron -n|-p|-s|-mmailcommand). The cron schedule. Defines when and at what frequency the subscription notifications will be sent. The format used is the 6-7 fields Quartz cron format. See Quartz documentation. A cron expression builder is available here.
Enter Email id in “Subscribe Emails” section then click add
Select and add alerts (one by one) to be subscribed by clicking “->” next to alert name in the “All alerts” section. (this is an optional step)
Click Next and Finish
Configure Subscription Groups to subscribe to alerts and receive notifications
Slack [API Support]
All notification channels are hosted within subscription groups. CRUD operations can be performed as usual on
subscription group entities using the
Step 1. Create a Slack App
Create a slack app for your workspace and add an incoming webhook. The webhook is tied to a specific channel and would look something like this.
Note that 1 app can support multiple incoming webhooks.
Optional: Subscription groups values can be populated via environment variables
To prevent the incoming webhook to be visible in plain text to any user, you can create an env variable (in kubernetes, you can also leverage secrets to do this).
Step 2. Create a subscription group
Here is a sample payload for creating the subscription group. You can submit this to
"cron": "*/1 * * * * ?",
Step 3: Use your subscription group with any Alert
The subscription group can be tied to any alert as usual.
Also note that 1 subscription group supports multiple specs. Therefore, it can route to the same or different notification channels in the same subscription group.