Channels

Users can use the following channels for receiving notifications:

• Email: Sends alert notifications directly to specified email addresses, providing detailed alert information in email format.

• Slack: Integrates with Slack workspaces to deliver real-time alert notifications to designated channels or direct messages.

• Webhook: Sends HTTP POST requests to custom endpoints, allowing integration with external systems and custom alert handling workflows.

• Microsoft Teams: Integrates with Microsoft Teams to send alert notifications to team channels or chat conversations.

• OpsGenie: Integrates with Atlassian OpsGenie incident management platform to create, escalate, and manage alerts through their on-call and incident response workflows.

Adding a Channel

Channels can be created independently of alert rules and reused across multiple alerts. To create a new channel:

1. Navigate to the Alerts section in the side panel

2. Select the Manage Channels tab (if not already selected)

3. Click the Create Channel button

After clicking Create Channel, you'll be presented with a Create Channel form to configure your notification channel.

Note: Channels are standalone configurations that can be created separately from alert rules. Once created, these channels can be assigned to multiple alert rules, providing flexibility and reusability in your notification setup.

Create New Channel

After clicking on the Create Channel button the user will be presented with a Create Channel modal to configure the notification.

Set up fresh notification channels with custom configurations.

Channel Configuration Fields:

• Name: User-defined name for the channel that serves as a unique identifier for easy recognition and management.

• Description (Optional): Additional details about the channel's purpose, recipients, or use case to provide context for other team members.

• Channel Type: Select the appropriate notification method based on your communication requirements:

  Channel Type	Description	Required Field
  Email	Direct email notifications	Email ID: email address
  Slack	Slack workspace integration	Webhook URL: Enter stack webhook URL
  Webhook	Custom HTTP endpoint integration	Webhook URL: Enter webhook URL Headers (Add): Key/Value pair
  Microsoft Teams	Microsoft Teams channel notifications	Webhook URL: Incoming webhook URL
  OpsGenie	Incident management and on-call alerting	API URL: OpsGenie's API endpoint API Key: Access token for OpsGenie's API

Channel Implementations:

This table outlines the different alert channel types available for notifications, along with references to their specific implementations and required fields.

Channel Type	Implementation	Required Field
Email	Add email address to the selected email alert channel.	Email ID: email address
Slack	See Sending messages using incoming webhooks	Webhook URL: Enter stack webhook URL
Webhook	See Channel-Webhook	Webhook URL: Enter webhook URL Headers (Add): Key/Value pair
Microsoft Teams	See Channel-Microsoft Teams	Webhook URL: Incoming webhook URL
OpsGenie	See Channel-OpsGenie	API URL: OpsGenie's API endpoint API Key: Access token for OpsGenie's API

Channel List

Once a channel is saved the same will be visible in the channel page in tabular view.

Users can search the channel names from the search box provided at the top right corner of the alerts table list and filter the entire list.

Note: The Manage Channels page displays all organization-level channels that are available across every site within your organization. These shared channels can be used by any site for sending alert notifications.

Channel actions

On a channel, users can perform certain actions which can be accessed by clicking on the three dots menu icon at the end of each channels list row:

• Edit Channel: Allows users to edit the channel rule. It will open the same Channel modal that was available while creating a new channel with form values pre filled.

• Delete Channel: Delete the channel from the system.

Use the Create Channel button to create a new channel.

Note: Channels that are currently assigned to active alerts cannot be deleted due to dependency constraints. If you attempt to delete a channel that's in use, the system will display an error message indicating this restriction.

To delete a channel in use:

1. First, either delete all alerts using that channel, or

2. Edit the associated alerts to reassign them to different channels

Once the channel is no longer referenced by any alerts, it can be safely deleted without disrupting the assigned set of alerts. Otherwise, you will get a Delete Channel notification.

Alerts Notification

Here is an example of an alert notification generated by the system on slack.

• Alert Name and Alert Type: The title of the notification provides the name of the alert provided by the user and the type of the alert.

• Description: An auto generated short description explaining the cause of the alert trigger.

• Alert Name: Name provided by the user at the time of alert configuration.

• Severity: Alert severity provided at the time of alert configuration.

• Alert Type: Type of the alert. If it is a Source no data exists, Site down, High CPU usage etc.

• Site ID: The Site is where the component at default is present.

• Component ID/Name: Component id and name which caused this alert.

• Component Kind: Type of component, source, destination or transform etc.

• Component Type: If the component is an AWS source, HTTP or Loki destination etc.

• Trigger Timestamp: Time at which the alert got triggered in the system.