Alerts

An alert rule watches one number in a project. When the number crosses your threshold, Rabolic opens an incident and tells your team.

Plans: alert rules are included on Growth, Scale and Business, and during the trial. On Starter, rules are kept but paused, and the page says which plan includes them.

Create a rule

Choose New alert. Owners, admins and analysts can create and edit rules.

How rules run

1. Every 5 minutes, Rabolic counts the metric for the window and for the window before, in production and without bots.
2. When the condition holds and the sample is big enough, an incident opens with both numbers and the change.
3. Everyone who can open the project is told, in the dashboard's notifications and by email, as each person's notification settings say. An incident that is still open doesn't send a second email.
4. When a later check finds the condition no longer holds, the incident is resolved by itself.

Incidents

The tiles show open and acknowledged incidents, active rules and how many triggered in the last 7 days. Incidents are under Open, Acknowledged and Resolved. Acknowledge or resolve one by hand with Acknowledge and Resolve.

The Alert rules table lists each rule with an on/off switch, its condition, window, minimum sample, cooldown and when it last triggered.

No events for an hour

On every plan, if a production project that usually sends events sends none for an hour, Rabolic notifies the team ("no events in the last hour"). Each person can turn these off under Ingestion problems in their notification settings.

Not available

Alerts go to the dashboard and by email only. Slack, Discord, Telegram and webhook channels, and anomaly detection, aren't built.