Set up alert rules and your notifications
Drafted from the screen's code on main (kareIntelligence 7455702). Not yet reviewed against a live session. Roles listed are the defaults the app's role matrix (@collabkare/ability 0.12.0) gives this screen's route; your organization's role overrides can change them.
Overview → Alerts holds the thresholds your organization watches, the history of what fired, and your own notification choices.
Rules
A rule is a metric, a comparator and a threshold, with an optional label. In the New rule form, pick a metric from the alertable catalog, set the comparator and threshold, and press Create rule. Each rule can be switched on or off with its Enabled checkbox, or removed with Delete (then Confirm delete). Rules are evaluated after every pipeline run and whenever someone presses Evaluate now. Deleting a rule keeps its fired events.
Recent events
Every fire, newest first — this is the alert log itself. Each row shows the observed value against the threshold, the rule (or "rule deleted — the event history is kept"), the evaluation run, and a Dispatch status (fired, dispatched, dispatch failed, or stored — dispatch not configured).
My analytics notifications
Two checkboxes decide what you are told, in-app, through the bell at the top of kareIntelligence:
- Alert rules fire for my organization
- Analytics runs finish (ETL, CQL evaluation) — success and failure
This is your own setting and changes nothing for anyone else. The card explains where your current state comes from. Run notifications have no server-side default: only your own choice subscribes you. The same card appears in Cloud Manager under Settings → My analytics notifications.
Things to know
- A rule whose metric has no value yet is skipped — never fired against a substituted zero.
- A rule that stays breached fires once per evaluating run; there is no suppression yet.
- Delivery is in-app only. Email and SMS are not available.