Configure alerts

Use alert rules to notify your team when Vercel detects error or usage anomalies.

To manage alert rules from the terminal, see vercel alerts rules.

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

1. Open Settings > Alerts for your team.
2. Click Add Rule.
3. Under Triggers, select the built-in alert type to configure:
   • Error anomaly: Trigger when a route's five-minute error count is unusually high compared to its recent baseline and passes Vercel's minimum activity checks.
   • Usage anomaly: Trigger when 5-minute usage is more than four standard deviations above the 24-hour average and crosses Vercel's minimum activity threshold.
4. Configure the trigger filters:
   • For Error anomaly, choose the HTTP group to monitor. By default, error anomalies track 5xx status codes. Select 4xx to monitor client error detections.
   • For Usage anomaly, choose the usage metric to monitor, such as Function invocations, Function duration, Function CPU duration, Fast Data Transfer, or CDN Requests.
5. Click Next.
6. In Configure alert rule, enter a rule name. This name appears in the Alert Rules table and notifications.
7. Choose the project scope for the rule. You can apply the rule to all projects, specific projects, or all projects except selected projects.
8. Click Create Alert Rule.

9. In Configure notifications, select one or more severity levels that should trigger notifications.

10. In Configure notifications, choose the notification destinations for the rule.
11. Click Done.

Vercel 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.

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

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

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

• Subscribe Team Owners: Automatically include team owners in Vercel Notifications.
• Configure Slack Channels: Route alerts to one or more Slack channels.
• Your Notifications: Set your own push, email, and Inbox subscriptions.
• Add Webhook: Forward alert events to a webhook destination from the Alerts settings page.

Configure Slack subscriptions per rule from the Alert Rules table.

1. Open Settings > Alerts for your team.

2. Create the rule, or select an existing rule.

3. In the Slack column, click Configure.

4. If the Vercel app for Slack is not installed for your team yet, install it first.

5. In Slack, open the channel that should receive alerts and invite the Vercel app:

   /invite @Vercel

6. In the same Slack channel, run the subscribe command shown in the modal. For a rule-specific subscription, Vercel includes the rule ID in the command:

   /vercel subscribe <team-id> alerts +rule:<rule-id>

7. Repeat this in any additional Slack channels you want to subscribe this rule to.

After a channel is subscribed, the rule shows the connected Slack channels in the Slack column.

Webhooks work outside individual alert rules. On the Settings > Alerts page, click Add Webhook to create a team webhook for alert events.

Webhook configuration applies at the team level. You can choose the endpoint URL and the projects that should send webhook events.

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