Beets
A beet is a single monitored event stream. It represents one thing you want to know is still happening in your application.
Creating a beet
Click + Add Beet in the sidebar. You’ll provide:
- Name — a descriptive identifier (e.g.
checkout.complete,cron.daily_digest) - Dashboard — which dashboard to attach this beet to
- Description (optional) — shown to the AI when generating alert explanations
Names are free-form. We recommend dot-separated namespacing (service.event) for clarity at a glance.
The beet detail page
Click a beet in the sidebar to open its detail page. It shows:
- Token — your ingestion token with copy/rotate controls
- Snippet — ready-to-paste HTML, JavaScript, and curl examples
- Open alert banner — appears when the beet is in a warning or critical state, with the AI Explain button
- Alert history — a chronological list of past alerts
- Widget area — your configured widgets
Beet status
Each beet has one of four states, shown as a pulsing dot in the sidebar and on the Status widget:
| State | Colour | Meaning |
|---|---|---|
learning | Grey | Less than 14 days of data — baseline not yet established |
healthy | Green | Event rate within expected range |
warning | Amber | Rate below baseline (non-critical) |
critical | Red | Rate severely below baseline or complete silence |
Locking
Beets beyond your plan limit are locked. Locked beets show a red padlock in the sidebar, still receive events, but their alert detection is paused. Upgrade your plan to unlock them.
Rotating the token
Use the rotate button on the beet detail page. The old token is invalidated immediately. All existing embeds using the old token will stop recording — update them promptly.
Deleting a beet
Beet deletion is not yet available from the UI. If you need to remove a beet, contact support or delete the row directly from your Supabase dashboard.