Skip to main content

Threshold alerts

An alert watches a number and emails a list of recipients when it crosses a threshold. Alerts live under Govern -- Alerts in the sidebar.

Alert types​

  • Data -- re-runs the query behind a card and reduces a numeric column to one value: the latest row, a sum, average, minimum, maximum, or a row count. Use it for business thresholds ("daily signups below 50").
  • Usage -- reads one of the organisation's usage metrics for the current day or month: dataset runs, dashboard views, dashboard exports or card data fetches, as a count or as bytes. Use it to hear about a spike before a usage limit bites.
  • System -- reads caching health over a recent window (24 hours by default): failed cache refreshes, total refreshes, or bytes processed. Pairs with cache windows.

Anatomy of a rule​

Every rule has the same spine:

  • a comparator and a numeric threshold -- the value is compared with one of: less than, less than or equal, greater than, greater than or equal, equal, not equal;
  • a cadence -- hourly, or daily at a time you choose (in your organisation's timezone);
  • a cooldown (default 24 hours) -- once an alert trips and emails, it stays quiet for the cooldown even if it keeps tripping;
  • a recipients list of email addresses;
  • an enabled toggle.

Evaluation and history​

A scheduler checks for due rules roughly every minute. Daily rules run once per day after their set time; hourly rules run at most once an hour. Every evaluation -- tripped or not -- is recorded in the rule's history with the measured value and the email outcome, and the most recent 50 events are shown alongside the rule.

Two test actions help you trust a rule before it matters:

  • Test evaluates the rule immediately and shows the value and whether it would trip. No email is sent and nothing is written to history.
  • Send test email sends a clearly-marked sample message to the rule's recipients so you can confirm addresses and delivery end to end.

Who manages alerts​

Anyone in the organisation can view the alert list and history. Creating, editing or deleting rules requires the Builder tier (T4) or above. Every create, update and delete is recorded in the audit log.

Availability​

Email delivery depends on the email service being enabled for your Flynt environment. Until it is, alerts still evaluate on schedule and every trip is recorded in the rule's history, but no email is sent -- the history and the Send test email action both report this state, so you can tell configuration apart from a delivery failure.