Drift alerts appear when Vertiqa detects a gap between what should be happening and what is actually happening. Examples include stale follow-up, blocked work, missed expectations, or rule-specific operating conditions.
Where drift fits
Drift is not a separate inbox. High-signal drift should route into Command Center so operators can review evidence and take action. The Drift admin surfaces are for understanding, tuning, enabling, disabling, and reviewing rule behavior.
Reviewing an alert
Check:
- the rule type and severity,
- why the alert matters,
- evidence and affected records,
- whether the alert is still current,
- the mapped action, if one exists,
- recent rule history and cost telemetry.
Act only when the alert points to real operating work. If the alert is valid but early, snooze it from Command Center. If it is not useful, dismiss it with a reason so future tuning has signal.
Tuning rules
Tune a rule when:
- too many low-value alerts are appearing,
- important issues are appearing late,
- operators repeatedly dismiss the same alert type,
- cost or latency is too high for the value of the rule.
Prefer threshold and scope changes before disabling a rule entirely.