Skip to content

Triage notifications

When triage classifies an event as ACTION, DXDT notifies your team through the channels you configure per severity. Routing is severity-based, so a critical incident and an informational blip can take different paths.

How it works

Each triage severity maps to a notification priority:

Severity Priority
CRITICAL P1
HIGH P2
MEDIUM P3
LOW, INFO P4

For each event, DXDT resolves the active channels in order: your per-severity configuration first; if you have configured nothing for that severity, the defaults apply:

Severity Default channels
Critical, High In-app + Slack
Medium, Low, Info In-app

Both configured and default channels are filtered by your plan tier. If filtering leaves no channel, delivery falls back to in-app — an alert is never dropped silently.

A triage notification carries the priority and category in its title, the triage summary as its body, and structured context: confidence, a reasoning excerpt, up to five suggested actions, and a link back to the event.

Channels

Channel Configuration Available on
In-app None All tiers
Slack Target channel (e.g. #alerts) Growth, Enterprise
Email Recipient list Growth, Enterprise
Webhook Destination URL, optional auth header Growth, Enterprise

Slack delivery uses your tenant's Slack workspace connection.

Using it

Open Triage → Channels. The tab shows a grid of severity rows (CRITICALINFO) against the four channels; toggle a cell to enable a channel for that severity. A configuration panel appears for each channel type you have enabled anywhere in the grid — set the Slack alert channel, email recipients, or webhook destination there.

The in-app notification bell

The bell in the page header shows an unread badge and the notification list. From it you can open a notification (triage notifications deep-link to the event), mark a single notification read, mark all read, or delete one. Unread counts update automatically while you work.

Configuration

Setting Where
Per-severity channel routing Triage → Channels
Slack alert channel Triage → Channels → config panel
Email recipients Triage → Channels → config panel
Webhook URL / auth header Triage → Channels → config panel

Troubleshooting

Symptom Cause
Slack/email/webhook enabled but only in-app arrives Channel not included in your tier — Starter delivers in-app only
Notifications arrive on channels you never configured No configuration exists for that severity, so the defaults apply
Slack enabled but nothing is delivered No Slack workspace is connected for your tenant
Trying to mute a severity entirely Not supported — when a severity has no active channel configuration, the defaults above apply