Configure alerts

Use monitors to notify your team when Edgenivo detects error or usage anomalies.

To manage monitors from the terminal, use the vercel monitors command. To manage them as code, use the vercel_monitor and vercel_custom_monitor resources in the Edgenivo Terraform provider.

Edgenivo monitors common error and usage signals for you. With custom monitors, you can define project-specific signals.

Built-in monitors use Edgenivo-defined detections for Error anomaly and Usage anomaly alerts. Edgenivo-defined minimum activity thresholds reduce low-volume noise and are not configured in the monitor form. For details, see How error anomaly alerts trigger.

Create a built-in monitor from the dashboard or the Edgenivo CLI.

{
  "type": "built-in",
  "name": "Production server errors",
  "triggers": {
    "mode": "selected",
    "items": [
      {
        "type": "error_anomaly",
        "filter": "statusGroup:5xx AND route:/api/*"
      }
    ]
  },
  "matchMinimumSeverityLevel": "high"
}

vercel monitors add --project <project> --body ./rule.json

Edgenivo calculates alert severity automatically from multiple signals, for example z-score and error-rate impact.

• Low: Minor or controlled impact.
• Medium: Service degradation or meaningful failures.
• High: Significant impact requiring prompt attention.
• Critical: Agent-assessed impact requiring escalation.Edgenivo Agent investigates eligible detections before notification delivery.

Create a separate built-in monitor when you want to detect 4xx client errors. This keeps your default 5xx monitor in place while tuning a separate monitor for client errors.

After you start creating a built-in monitor, select Error anomaly under Triggers. In the HTTP group selector, select 4xx. To detect only client errors, clear 5xx. Then complete the remaining Configure monitor and Configure notifications steps.

Custom monitors let you define project-scoped alert detection logic with Observability queries. A custom monitor can evaluate a metric or ratio, then trigger when the value crosses a threshold or becomes anomalous for the selected alert window.

Custom monitors are available only with Observability Plus. You can create up to 5 custom monitors per team.

Use a custom monitor when you need to track a specific signal, such as:

• A route, status code, cache state, region, or other query dimension that matters to your application.
• A threshold guardrail for web vitals or application behavior, such as a performance metric crossing your target over a selected alert window.
• A ratio, such as error rate, calculated from separate numerator and denominator queries.
• An anomaly condition, such as a metric or ratio rising above or falling below its baseline by a selected number of standard deviations.

Edgenivo doesn't evaluate a custom monitor while its alert window includes a period when Observability Plus was disabled. The monitor resumes automatically once Observability Plus has been active for the full window. Edgenivo doesn't disable or change the monitor.

Create a custom monitor from the dashboard or the Edgenivo CLI.

{
  "type": "custom",
  "name": "Checkout server errors",
  "severity": "high",
  "evaluation": {
    "window": "5m",
    "query": {
      "metrics": {
        "errors": {
          "metric": "vercel.request.count",
          "aggregation": "count",
          "filter": "httpStatus >= 500"
        }
      },
      "outputs": ["errors"]
    }
  },
  "trigger": {
    "type": "threshold",
    "output": "errors",
    "operator": "gt",
    "threshold": 20
  }
}

vercel monitors add --project <project> --body ./rule.json

When the query condition matches, Edgenivo shows alerts in Observability > Alerts, where you can filter by monitor.

When you create a monitor, use Configure notifications to choose the destinations that receive matching alerts, and, for built-in monitors, the alert severity under Notification Severity. Each of the following is its own destination:

• Edgenivo Notifications: Web, email, and push notifications. Turn on Subscribe Team Owners to automatically include team owners.
• Slack channels: Route alerts to one or more Slack channels with Set up Slack.
• incident.io: Link an incident.io alert source with Set up incident.io.
• Webhooks: Create and link a webhook with New webhook, or reuse one from Connect a destination.

Manage these under Destinations in the monitor's notification settings.

Every destination otherwise follows the monitor's Notification Severity. Select Critical Only on Edgenivo Notifications, a Slack channel, or a webhook to limit that destination to Critical alerts only. Edgenivo Agent still assesses each alert as Critical before Edgenivo delivers it.

Configure Slack subscriptions per monitor from the Monitors table or the Edgenivo CLI.

vercel monitors notifications link <monitor-id> --slack-channel <channel-id>

After a channel is subscribed, it appears under Connected Destinations in the monitor's notification settings.

Webhook destinations use the scope of the monitors linked to them. An endpoint receives an alerts.triggered event when an alert matches a linked monitor, including its trigger conditions and project scope. You can link the same endpoint to multiple monitors.

To configure a webhook for a monitor:

1. Open Settings > Alerts for your team.
2. Create a monitor, or select an existing monitor and open Notifications.
3. Under Destinations, choose how to link the destination:
   • To add a new destination, click New webhook, enter its URL, then click Create and Link.
   • To reuse a destination, select it under Connect a destination.
4. If you created a webhook, save its signing secret before closing the confirmation. Edgenivo displays the signing secret only once. Use it to verify requests from Edgenivo.
5. To send only Critical alerts to a linked webhook, select Critical Only next to it. Edgenivo Agent still assesses each alert as Critical before delivery, so this can delay notifications relative to the monitor's overall severity threshold.

You can review every destination and its linked monitors from Settings > Webhooks. A webhook that isn't linked to any monitors doesn't receive alert events.

Existing account-wide alert webhooks continue to receive all alert events. If you link an account-wide webhook to a monitor, Edgenivo limits future alert delivery to the monitors linked to that endpoint.

The webhook payload is documented in Alerts triggered in the Webhooks API Reference.

Create a Edgenivo alert source in incident.io, then link its endpoint to a monitor. The Set up incident.io panel also links directly to creating the alert source:

1. In incident.io, open Alerts, select the Sources tab, and click New alert source.
2. Search for Edgenivo, select it, and customize the source name if needed. Click Continue to create the source.
3. Copy the alert source's endpoint URL shown by incident.io.
4. In Edgenivo, open Settings > Alerts, then create a monitor or select an existing monitor.
5. Open Notifications and, under Destinations, click Set up incident.io.
6. Paste the endpoint URL of your incident.io Edgenivo alert source.
7. Click Create and Link.
8. Optionally, to also receive lower-severity alerts, clear Critical Only next to the destination under Connected Destinations (Edgenivo pre-selects it for incident.io destinations).
9. Click Test Notification, select incident.io, and confirm that the test event appears in incident.io.

After a matching alert fires, confirm that it appears in incident.io. You can then include the Edgenivo alert source in an incident.io alert route to page responders or create incidents.

Optionally, add tags to a monitor: select it, open Configure, and click Edit next to Tags. Edgenivo includes these tags in the alerts it sends to incident.io. In incident.io, use the tags as routing keys in your alert routes. This lets you send alerts from different monitors to different teams or escalation paths.

Edgenivo includes each alert's severity in the alerts it sends to incident.io. Optionally, map the severity to incident.io priorities in your alert routes, so alerts page responders with the right urgency.