Alerts
The Alerts rail lists velocity spikes, regressions, ingest cap hits, and other issue lifecycle events without opening every Issues row. Channels deliver them to Slack, Discord, Telegram, email or a signed webhook.
What can fire an alert?
Built-in kinds (filter chips in the UI):
| Kind | Typical meaning |
|---|---|
new_issue | First event for a fingerprint |
velocity_spike | Event rate jumped in a rolling window (default 15 minutes, ratio > 4× vs the previous window, which needs at least one event) |
regression | Resolved-in-release issue came back on a newer release |
event_milestone | Occurrence count crossed a rule threshold |
users_affected | Unique users crossed a rule threshold |
ingest_cap_hit | Project hourly ingest cap reached (403 on further ingest) |
custom | Custom alert rules you define in the rules panel |
Tune velocity window with EPURE_VELOCITY_WINDOW_SECS on the server: Configuration.
Spike valve ≠ velocity alert
The spike valve (~100 events/min/fingerprint) still returns 202 and may drop duplicate bodies. Velocity alerts compare windows over minutes and show in the Alerts rail — different mechanism: Concepts.
Alerts vs webhooks vs snooze
| Mechanism | Purpose |
|---|---|
| Alerts rail | In-app unread/history, mark read, jump to issue |
| Channels | Slack, Discord, Telegram, email, or a signed generic webhook |
| Snooze | Mute an issue (time, occurrences, or users) — does not delete alerts history |
Webhook event ids include issue_created, regression, and velocity_spike. Setup: Webhooks API and Settings.
Velocity spike (operator mental model)
- Epure tracks timestamps per issue in memory.
- When the current window’s count vs the previous window exceeds the ratio threshold, it inserts a
velocity_spikealert (and may enqueue webhook dispatch when subscribed). - Use it to catch deploy regressions and traffic floods before manual triage.
Regression alerts tie to resolve in release workflow: Releases.
Ingest cap alerts
When a project exceeds ingest_cap_per_hour (default 5000), further ingest returns 403 ingest_cap_exceeded. Epure may also record an ingest_cap_hit alert so operators see saturation in the rail — not only failed SDK posts.
Raise the cap or fix the logging loop: Projects, API errors.
Agent API
Automation can list alerts with a personal access token: GET /api/v1/agent/alerts. See Agent API.
FAQ
Why did I get a velocity alert but Issues looks quiet?
The alert fired on a rate change for one fingerprint. Open the alert row to jump to the issue and check the environment filter and time window. Snoozed issues send no new-issue, regression, milestone or velocity alert until the snooze ends.
Can I pause a rule?
Use the rules panel in Alerts to pause built-in or custom rules per project. Ignored alerts move to the Ignored view without deleting history.
Do alerts email me?
Yes, if you add an email channel with its recipients. Alerts always show in the in-app rail; channels (Slack, Discord, Telegram, email, signed webhook) deliver the kinds you pick.