Alerts
Alerts are available on Enterprise and Pro plans with Observability Plus
Alerts let you know when something's wrong with your Edgenivo projects, like a spike in failed function invocations or unusual usage patterns. You can get these alerts by email, through Slack, or set up a webhook so you can respond to issues.
By default, you'll be notified about:
- Usage anomaly: When your project's usage exceeds abnormal levels.
- Error anomaly: When your project's error rate of function invocations exceeds abnormal levels.
Edgenivo-defined minimum activity thresholds reduce low-volume noise and are not configured in monitors. For details, see How error anomaly alerts trigger.
| Alert Type | Triggered when | Grouping |
|---|---|---|
| Error Anomaly | Fires when a route's five-minute error count is unusually high compared to its recent baseline and passes Edgenivo's minimum activity checks. By default, error anomalies track 5xx status codes, but monitors can be configured for 4xx detections. | Route, HTTP status group |
| Usage Anomaly | Fires when your 5-minute usage is more than 4 standard deviations above your 24-hour average and crosses Edgenivo's minimum activity threshold. For Function invocations, Function duration, and Function CPU duration, usage combines metrics from Edgenivo Functions and Routing Middleware. | Metric |
Beyond these built-in alert types, custom monitors let you define project-scoped detection logic with Observability metric or ratio queries, triggering when a value crosses a threshold or becomes anomalous for the selected alert window. Custom monitors are available only with Observability Plus.
Usage anomaly alerts support these metrics:
- CPU duration
- Duration
- Invocations
- Fast Data Transfer
- CDN Requests
Alerts only use data collected while Observability Plus was active. After you enable or re-enable Observability Plus, Edgenivo holds back alerts until it has enough data, which avoids false positives:
- Error anomalies, including external API failure insights, start after Observability Plus has been active for 24 hours.
- Usage anomalies start after Observability Plus has been active for 3 days.
If you disable Observability Plus for your team or for a project, alerts stop for that scope. When you re-enable it, the activation periods start again.
Use Configure alerts to create built-in monitors, set notification destinations, and configure Slack or webhooks.
You can also configure custom monitors with project-scoped Observability metric or ratio queries.
When you get an eligible Medium or High anomaly alert, Edgenivo Agent Investigation can run automatically. Low-severity alerts do not start automatic investigations.
In the investigation panel, click Configure Edgenivo Agent to manage automatic investigations. You can also run an investigation manually.
Learn more in the Agent Investigation docs.
Edgenivo compares each completed five-minute interval with the route's trailing 24-hour baseline. These examples assume default sensitivity:
| 24-hour baseline | Current five-minute interval | Result |
|---|---|---|
| About 1,000 requests per interval, about 1% errors, and low variance | 1,000 requests and 100 errors | A high-impact anomaly triggers after the current interval |
| About 1,000 requests per interval, about 1% errors, and low variance | 1,000 requests and 40 errors | A lower-impact anomaly waits for the next interval, then triggers if the trailing two-interval validation passes |
| Similar average traffic and error rate, but with recent error spikes | 1,000 requests and 100 errors | The anomaly might not trigger if baseline variance keeps it below the threshold |
Actual results depend on baseline traffic, error rate, variance, and statistical confidence checks. Error counts alone do not guarantee an alert. The following interval does not need to contain another unusual spike, and alerts based on two intervals reflect data from both.
Was this helpful?