Vercel Observability gets custom monitors with threshold alerts
New custom monitors let you alert on any Observability metric, from AI Gateway costs to Sandbox CPU time, using a threshold or anomaly detection instead of the built-in alert set.
Vercel added custom monitors to Observability on 26 October, letting you define your own alerting rules instead of relying on the built-in set. A monitor tracks a single metric, such as response time, or a ratio between two, such as errors divided by total requests, and you choose either a fixed threshold or statistical anomaly detection, with its own detection window, filters and grouping.
Vercel’s own examples include AI Gateway costs, Core Web Vitals, Workflow and external API failure rates, and Vercel Sandbox CPU time. Alerts can go to email, Slack, Vercel Inbox, push notifications or team-level webhooks, and you can attach context for Vercel Agent to use when it investigates one. You build monitors in the UI under Settings > Alerts, from an existing chart, from a preset, or as JSON via vercel monitors add in the CLI. They need Pro or Enterprise with Observability Plus, and cost $0.0035 per GB of data scanned; the alerts built into Observability Plus stay free.
vercel monitors addWhy it matters: a fixed alert set only covers what the vendor thought to add. Custom monitors mean you can wire up alerting for whatever actually matters to your product, like AI Gateway spend creeping up or Sandbox CPU time spiking, rather than waiting for Vercel to ship it as a default.