Alerts watch your data for you, so you don't have to refresh a dashboard to catch a problem. Set up rules once, and UMAP360 keeps an eye on the metrics that matter — flagging unusual spikes, drops, or threshold breaches and emailing you a digest with links straight back to the relevant data.
What alerts do
An alert rule watches a metric and notifies you when something is off — for example, when ingestion stalls, event volume drops, or data quality slips. You decide what to watch, how often to check, and where the notification lands.
You'll find Alerts in the 360 Tools hub: open the hub from the sidebar and click the Alerts tile, which opens the Alerts page. Alerts are available to everyone on your team, regardless of role.
Where Alerts lives
Alerts used to sit under Settings. It now lives in the 360 Tools cluster. Old Settings → Alerts bookmarks redirect to the Alerts page automatically, so you don't need to update them.
The Alerts page at a glance
The page is split into two columns:
- Alert Rules (left) — your list of rules. Each one shows the metric it watches, its condition, how often it's checked (hourly or daily), and how you'll be notified. You can toggle a rule between active and paused, delete it, or create a new one with + New Rule.
- Alert History (right) — every time a rule fired, newest first. Each entry shows a severity pill (CRITICAL or WARNING), how long ago it triggered, a short description of what happened, and small icons showing how the alert was delivered.
Creating a rule
Use + New Rule to add an alert. For each rule you choose:
- The metric to watch.
- The condition that should trigger it.
- Check frequency — hourly or daily.
- How you're notified — in-app, email, or both.
Once saved, a rule starts watching right away. Use the inline toggle to pause a rule temporarily without deleting it — handy during a known maintenance window or a planned spike.
Pause, don't delete
If a rule is noisy for a known reason, pause it rather than deleting it. Pausing keeps the rule (and its history) intact so you can switch it back on with one click.
Reviewing alert history
Alert History is your record of everything that fired. The most recent entries load first, and severity is colour-coded so the critical items stand out. The delivery icons next to each entry confirm how you were notified.
When there's a lot of history, a Load more alerts button appears at the bottom so you can page back through older events.
The daily digest email
Rather than emailing you on every single trigger, UMAP360 batches alerts into a once-daily digest. You get one email summarising the alerts since the last digest — sorted critical-first, then newest-first.
The email lays everything out in a simple table: the severity, which rule fired, the metric, its current value, the baseline it was compared against, when it triggered, and a View → link. Clicking View → opens the Alerts page already filtered to the alerts in that digest, and scrolls straight to the specific alert and highlights it — so you land on exactly the data you need to act on.
Subject lines tell you what's inside at a glance:
- A single alert names the rule and condition directly.
- A batch of alerts summarises the count, like "5 alerts — 2 critical, 3 warnings".
Jump straight from the email
Every row in the digest links back into the product. Click View → to open the exact alert in context instead of hunting for it manually.
Tips
- Start with a couple of high-signal rules (for example, a drop in incoming events) rather than alerting on everything at once.
- Use hourly checks for things you need to react to quickly, and daily for slower-moving trends.
- Keep an eye on the unread count shown on the Alerts tile in the 360 Tools hub — it's a quick prompt to review what fired.
Next steps
- Connector health and troubleshooting — when an alert points to a data-source problem.
- Events and the dictionary — inspect the underlying event data behind an alert.
- Dashboards overview — see the full set of dashboards and where Alerts fits in.
- Troubleshooting — if alerts aren't arriving as expected.
Last updated 2026-06-11