Alerts and cost
Notifications
The bell in the top bar, the ten kinds of notification it collects, where each one links, and how read and unread work.
The bell collects what happened while you were away. Each item links to the run, trace, queue or rule it is about.
The bell
The bell is in the top bar of every project page. Its badge counts your unread notifications, up to 99+, and refreshes every minute while the tab is visible, and at once when you come back to the tab. The list shows the newest first, with Unread only on by default; turn it off to see read items. Each row has the kind, a title, a short body and the time. Clicking a row marks it read and opens its link. Mark all read clears the badge and deletes nothing. Read state is per person, so marking yours read changes nothing for anyone else.
The ten kinds
| Kind | Written when | Who receives it | Links to |
|---|---|---|---|
| Mention | a comment mentions you | the members it mentions, except the author | the trace, span, session, run or dataset row the comment is on |
| Alert fired | an alert rule fires | Owners, Admins and members whose email is on the rule | Alerts, History tab |
| Monitor signal | a monitor finds an anomaly or regression | Owners, Admins and members whose email is on the monitor | the monitor, on the Alerts Monitors tab |
| Budget paused | an online rule reaches its daily judge budget | Owners and Admins | Evaluations, Online rules tab, for that Environment |
| Run completed | an evaluation run you started completes | the person who started it | the run |
| Simulation finished | a simulation run you launched ends | the person who launched it | the simulation run |
| Review assigned | review queue items are assigned to you | the assignees | the queue, in Annotate |
| Access requested | someone asks to join the organization | Owners and Admins | the request, in organization settings, Members |
| Usage threshold | an Environment passes 80% or 100% of its monthly span limit | Owners and Admins | Alerts, History tab |
| Plan changed | a platform admin changes the organization's plan | the organization Owner | organization settings, Plan & usage |
Storing a notification never holds up the event behind it: a run completes even if its notification could not be saved. A pass rate with no value reads "no verdict", not 0%. Four kinds also arrive outside the bell. Alert rules and monitors send email and Slack messages to their own recipients, described in Alerts. Usage notices are emailed to the organization Owner, and a mention emails each member it names. The other kinds appear only in the bell.
Limitations
- The badge polls, so a new item can take up to 30 seconds to appear.
- The list covers every organization and project you belong to and has no scope filter, so opening an item can take you into another project.
- You cannot mute a kind, get a digest or mark an item unread again. To find a row you read by accident, turn off Unread only.