Alerts
Alerts tell you when a count of events crosses a line, rises or falls against the usual, stops, or when a new error appears. Each alert reruns a saved query every few minutes; no AI is involved in checking it. Alerts are an add-on: $29 once on Core, and included in the trial.
Make an alert
Open Alerts in the menu and press New alert. Or ask in chat, or in Claude over MCP: "tell me if payments stop for an hour" makes the alert for you.
| Tell me when | Example |
|---|---|
| A count crosses a line | More than 20 events with level error in 15 minutes |
| A count rises or falls against the usual | Signups in the last hour fall by 50% against the same hour on the last 7 days |
| Nothing arrives | No payment events for an hour |
| A new error appears | A log line that looks like an error and was never seen before |
Count events or distinct visitors, and narrow the count with conditions on the event name, pattern name, level, route, path, status code, source or kind. Check it now shows what the rule would say at this moment, so you can pick a line from real numbers. A change alert stays quiet while the usual count is below 10, so a handful of events cannot swing it.
An alert sends once when its rule becomes true, and again when it is back to normal. Each alert keeps a history of when it fired and resolved, where it was sent, and notes from the team, such as what caused it. Editors and admins make and change alerts; everyone can read them.
Where alerts go
An admin adds channels in Settings, Alerts. Every channel has Send a test.
- Email goes through your own email server or a service such as Postmark, SES, Resend or Gmail, over SMTP. Fill in the server, port, security, user name, password and sender once, on the same page, and send a test email.
- Slack: add the Incoming Webhooks app to a Slack channel and paste its address, which starts with
https://hooks.slack.com/. - Webhook: StatsRaven sends a JSON POST to any address, for an incident tool or your own code.
Links in messages open StatsRaven at the address an admin uses. Change it in Settings, Alerts if people reach StatsRaven at another address.
Webhook format
{
"type": "alert.fired",
"alert": { "id": 3, "name": "Payments stopped", "project": "shop", "kind": "absence", "rule": "No events in 1 hour" },
"value": 0,
"text": "No events in the last 1 hour.",
"link": "https://stats.example.com/alerts?alert=3",
"at": "2026-11-20T21:04:00Z"
}
type is alert.fired, alert.resolved, alert.test, digest.daily or digest.weekly. With a signing secret, each request carries x-statsraven-timestamp and x-statsraven-signature: sha256=<hex>, the HMAC-SHA256 of the timestamp, a dot and the body:
// Node.js: compare before trusting the body
const expected = "sha256=" + crypto.createHmac("sha256", secret).update(timestamp + "." + rawBody).digest("hex");
Digests
A digest sends yesterday, or the last week on Mondays, at the hour you pick in UTC: visitors, events and errors against the period before, the most viewed pages, alerts that fired and what moved. Add one at the bottom of the Alerts page; Send now shows what it looks like.
Insights
Each morning StatsRaven compares yesterday with the average day of the week before, for visitors, errors and your busiest event names, and notes what moved by 30% or more. The notes show under Worth a look on the Alerts page and in digests. No AI is used.
Without the add-on
Alerts can still be made, from the page, chat or MCP. They wait as drafts and start as soon as a license with Alerts is applied in Settings, License. The Alerts page and Settings, License link to buying it.