Skip to content
FlagSwiftDocs

Alerts

Rules that tell you when errors climb, responses slow down or releases fail.

What this page is for#

An alert rule watches one measure for a project, and optionally one environment. Rules are checked every minute and appear on this page and on the Overview. If the server has a webhook URL set, a firing alert is posted there, and with an email provider set up it is also emailed.

In the console it lives at /alerts. You see it in the sidebar when your role has alerts.read.

What you can do#

  • Create a rule

    Name it, choose a project and environment, and pick what to watch.

  • Choose the measure

    Evaluation error rate, Latency p95, Evaluation volume drop, Evaluation volume spike or Release failures.

  • Set the threshold

    Say when it fires (at or above a value), over how many hours, and a minimum number of requests so quiet periods never fire.

  • Pause or resume

    Each rule card has a switch to pause or resume it.

  • Edit or delete

    Change a rule, or delete it along with its history.

Good to know#

  • Reading alerts needs alerts.read. Creating, editing, pausing and deleting need alerts.manage.
  • A rule shows its state as OK, Firing or Not enough data, and says when it has not fired yet.
  • The Alerts link in the sidebar shows how many rules are firing in red, or a red dot when the sidebar is collapsed. The page refreshes itself every minute without showing a loading state.
  • Email for a firing or resolved alert goes to the people who hold alerts.manage.
  • A rule stays with its project once created.
  • New rules need at least one project.