Contents

Alert channels

An alert rule says what to watch: a new error group, a regression, a confirmed incident, a release that brings new errors, a monitor that goes down. Its channels say where the alert goes. Rules live under Settings, Alerts; open a rule and use Edit channels.

Weekly digest

Observer Usage can send a weekly email or Slack digest on your chosen weekday and UTC hour. It covers new, regressed and resolved error groups, merged fixes, monitor uptime, the noisiest groups, and ingest against quota. Empty sections are omitted, and a week with nothing to report sends nothing. Overlapping sweeps share a conditional send claim, so the digest arrives once.

Anomaly alerts

A log volume or error-rate anomaly rule compares the latest complete 15 minutes with the same hour over the previous seven days. It needs at least three days of history and 20 events in the current window. Low, medium and high sensitivity control how far from the baseline is too far. A rule resolves after two normal evaluations. Until it has enough history, its state is Learning and it never fires.

In the app, Slack and webhooks

Every alert lands in the app’s notifications. Slack posts to a channel through the connected Slack integration. A webhook receives a JSON body signed with the workspace’s signing secret, so your endpoint can check it came from e-volv.

Email

Pick workspace members, type addresses, or both. Each email names the rule, what fired, the values and the time, with a link back to Observer. A rule sends at most one email every 15 minutes by default (you can change it), so a burst does not flood an inbox. When the alert clears, the same people get a recovery email.

PagerDuty

Paste an Events API v2 integration key. It is stored encrypted and never shown again; the page shows only its last four characters. When an alert fires, PagerDuty gets a trigger; when it clears, a resolve. Both carry the same dedup_key, built from the rule and what it is about, so the same problem firing again updates one incident instead of opening another.

Test before you rely on it

Send test email and Send test event sit next to the settings. The PagerDuty test is an info-level trigger that resolves straight away.

Email and PagerDuty are part of e-volv Observer. A workspace without it sees the options disabled, and a rule stops delivering to them if the subscription lapses. In the app, Slack and webhooks keep working.

Monitors use the same channels; see Monitors.

We use only essential cookies to keep you signed in and the app working. With your consent we may enable optional analytics to help us improve e-volv. See our Privacy Policy and Terms.