Alert channels
The destinations an alert rule can deliver to, and what each one needs before it will work.
Alert channels
An alert rule delivers through one or more channels, added in Set up alert channels while you build the rule. Email works with nothing but an address. The other three connect Decube to a system you own, so each needs a one-time setup on that side before the rule can reach it.
The address to notify
Nothing
Slack
The channel to post in
Authorize your Slack workspace, once per organization
Webhook
An https:// endpoint, plus optional headers
An endpoint that accepts our payload
Microsoft Teams
The Teams webhook URL
A Workflow on the Teams channel that produces that URL
One rule can carry several channels, including more than one of the same type, so a single incident can post to Slack and email a team at the same time. Use Add a new channel to keep adding rows, and the minus control on a row to remove one.
Select Email on a channel row and enter the address to notify. Each email covers one incident and gives you the monitor that failed, the asset it watches, the evidence captured at the moment of failure, and a link through to the case.
If Decube reports the alert as delivered and nothing reaches the inbox, the message is being filtered on the receiving side. Ask your email administrator to allow Decube's alert sender alerts@decube.io.
Test alert
Every channel row has a Test alert button. It sends a fixed sample message through the real delivery path, so a message arriving confirms the destination is wired up correctly. A test send skips rule evaluation and carries no incident data, so it tells you the plumbing works rather than whether your rule matches anything.
Where delivery is recorded
Every case shows the destinations its alerts went to and whether each delivery succeeded, so you can tell a rule that never matched from a channel that refused the message.

Set up a channel
SlackMicrosoft TeamsWebhookLast updated