alerts.evaluate · every 5 min
Hear about it when a number moves, not a week later.
Set a rule on the numbers that matter: events, sessions, conversions or revenue. Rabolic checks it every five minutes against the window before, and emails your team when it trips.
- Above, below or change by %
- Email and in-app
- Closes itself when it recovers
Checkout conversions dropped
SeriousAcme Fit · production
- Metric
- Conversions
- Condition
- Changes by 30%
- Window
- Last 6 hours vs the 6 before
- Minimum sample
- 50
- Cooldown
- 4 hours
6 hours before
41
Last 6 hours
18 −56%
Incident open · checked at 18:05
Email · to 4 members
Acme Fit: Checkout conversions dropped
conversions: 18 in the last 6h, 41 before (-56%).
app.rabolic.com/acme/acme-fit/alerts
In the dashboard for everyone who can open Acme Fit
AlertDefinition
Six fields, one rule.
A rule belongs to one project. It says what to watch, when it counts as a problem, and how loud to be about it. Owners, admins and analysts can write rules; viewers see what they find.
| Metric | Events (all, or one event by name), sessions, conversions or revenue |
|---|---|
| Condition | Goes above a value, drops below a value, or changes by a percentage either way |
| Window | The last hour, 6 hours or 24 hours, compared with the same length of time before it |
| Minimum sample | Nothing fires until the numbers are big enough to mean something. 50 by default |
| Cooldown | How long to stay quiet after an alert, from 15 minutes to 7 days. 4 hours by default |
| Severity | Critical, serious, warning or info, shown on the incident |
*/5 * * * *
What happens every five minutes.
- :00
Checked
Every five minutes, the metric is counted for the window and for the window before, in production and without bots.
- trip
Incident opened
When the condition holds and the sample is big enough, an incident opens with both numbers and the change.
- notify
Team told
Everyone who can open the project gets it in the dashboard and by email, unless they turned that off.
- recover
Closed by itself
When a later check finds the condition no longer holds, the incident is resolved. You can also acknowledge or resolve it by hand.
plans
Included in Growth, Scale and Business, and during the trial.
Rules of an organization without alerts on its plan are kept, paused, until the plan includes them again. Separately, every plan gets an incident when a project that usually sends events goes quiet for an hour.
Compare plans- StarterNo alerts
- GrowthAlerts
- ScaleAlerts
- BusinessAlerts
- TrialAlerts
good to know
The edges of a rule.
- Email and in-app only
- Slack, Discord, Telegram and webhooks aren’t available as destinations.
- Production data
- Rules count production events and leave bots out, like your reports.
- Counts, not rates
- A rule watches a count or a sum. Conversion rates, funnels and unique users can’t be alerted on.
alerts faq
Alerts, answered.
Which plans include alerts?
Growth, Scale and Business, and during the trial. Rules of an organization on a plan without alerts are kept but don’t run until the plan includes them again.
What can an alert watch?
The count of events (all of them, or one event by name), sessions, conversions or revenue in a project, over the last hour, 6 hours or 24 hours.
How often are rules checked?
Every five minutes. Each check compares the window that just ended with the same length of time before it.
How do I stop alerts from being noisy?
Each rule has a minimum sample, so small numbers don’t trigger it, and a cooldown, so it stays quiet for a while after it fires. An incident that is still open never sends a second email.
Where are alerts sent?
To everyone in the organization who can open the project: in the dashboard’s notifications and by email. Each person can turn either off for alerts. Slack, Discord, Telegram and webhooks aren’t available.
Who can create alert rules?
Owners, admins and analysts. Viewers see the incidents but can’t change rules.
Does Rabolic tell me when my SDK stops sending?
Yes, on every plan. If a production project that usually sends events sends none for an hour, Rabolic opens an incident and tells the team, and closes it when events arrive again.
Let the numbers tell you when they move.
Start a 3-day trial without a card. It begins with your first event, so you can set up the SDKs first.
- 1
Create a project
Sign up, name your project, and copy its publishable key.
- 2
Add an SDK
Web, React Native, Flutter or Node.js, or the HTTP API. Or run npx rabolic init.
- 3
Watch the first event arrive
It shows in live events within seconds, and your trial starts then.