Notifications
The bell in the top bar: the ten kinds of notification it collects, how to get from an item to the run, trace or rule it is about, and how mark read works.
After this page you can find out what happened while you were away and get to the run, trace, queue or rule it happened on in one click — and you know which events reach the bell and which also reach your inbox.
The bell
The bell sits in the top bar of every project page and shows a badge with your unread count (capped at 99+), refreshed every 30 seconds while the tab is visible. Opening it lists your notifications newest first — Unread only by default, Show all for history — each with its kind, title, a one-line body and time. Clicking an unread row marks it read and follows the stored link; Mark all read clears the badge without deleting anything. Notifications are per person: marking yours read never affects a colleague’s.
The ten kinds
| Kind | Written when | Who receives it | Links to |
|---|---|---|---|
| Mention | a comment mentions you | the mentioned members, minus the author | the comment on its trace, span, session, run or row |
| Alert fired | an alert rule fires | organization Owners and Admins, plus the addresses on the rule | Alerts › History |
| Monitor signal | a monitor detects an anomaly or regression | the same | Alerts › Monitors |
| Budget paused | an online rule reaches its daily judge budget | Owners and Admins | Evaluations › Online rules for that Environment |
| Run completed | a run you started finishes | the run’s creator | the run |
| Simulation finished | a simulation run you launched ends | the creator | the run |
| Review assigned | items are assigned to you in a review queue | the assignees | Annotate › the queue |
| Access requested | a non-member asks to join the organization | Owners and Admins | Organization › Members |
| Usage threshold | an Environment passes 80% or 100% of the monthly span allowance | Owners and Admins | Plan and usage |
| Plan changed | a platform admin changes the organization’s plan | Owners and Admins | Plan and usage |
A notification is written by the event that caused it and never fails that event: a run completes whether or not its notification could be stored. Pass rates in a notification read no verdict when null, never 0%. Alerts, monitors and usage notices also go out by email and Slack — see Alerts — and the bell is additive to those channels, never the only one.
Limitations
- The badge polls; an item can be up to 30 seconds late.
- The list is person-wide across every organization and project you belong to, with no scope filter, so one click can move you into another project.
- There are no per-kind mute or digest preferences, and no mark-as-unread: a row read by accident is found again under Show all.