# Create custom monitors in Vercel Observability

Source: [Vercel](https://vercel.com/changelog/create-custom-monitors-in-vercel-observability)  
Feed7 permalink: https://feed7.dev/p/create-custom-monitors-in-vercel-observability-00px5cw  
Published: 2026-10-26T06:00:00.000Z  
Trust: Official Source (official_source)

## Why Included

Vercel Observability custom monitors can alert on individual metrics or metric ratios, using thresholds or anomaly detection. Builders can configure them in the UI or CLI and route alerts to several channels.

## Source Summary

Custom monitors in Vercel Observability track a single metric or a ratio, with **anomaly detection or fixed thresholds**. They can cover AI Gateway costs, performance, failure rates, and Sandbox CPU time.

## Practical Implication

Builders can configure detection windows, filters, and grouping, then create monitors in the UI or with the **Vercel CLI**. Alerts can reach email, Slack, Vercel Inbox, push notifications, or team webhooks; Vercel Agent can receive investigation context.

## Agent-Ready Context

Custom monitors in Vercel Observability track a single metric or a ratio, with **anomaly detection or fixed thresholds**. They can cover AI Gateway costs, performance, failure rates, and Sandbox CPU time.

Builders can configure detection windows, filters, and grouping, then create monitors in the UI or with the **Vercel CLI**. Alerts can reach email, Slack, Vercel Inbox, push notifications, or team webhooks; Vercel Agent can receive investigation context.

The feature is for Pro and Enterprise plans with Observability Plus. Scans cost **$0.0035 per GB**; built-in alerts remain included with Observability Plus.

## Connected Context

Feed7 judgment across 928 accumulated Signals:

Custom monitors add configurable anomaly or threshold alerts for operational metrics, including AI Gateway costs, failures, performance, and Sandbox CPU time. Vercel Agent can receive investigation context, linking detection to agent-assisted follow-up; availability and scan charges define practical adoption constraints.

- [Agent Runs now available in the Vercel MCP and CLI](https://feed7.dev/p/agent-runs-vercel-mcp-cli-06cfo04) — Custom monitors can surface investigation context, while Agent Runs exposes traces and usage data; together they connect operational alerts with evidence about agent behavior.
- [Always-on agents run production without the on-call tax — Justin Smith, Resolve AI](https://feed7.dev/p/always-on-agents-run-production-without-the-on-call-tax-justin-smith-res-06ukqzk) — Always-on production agents rely on bounded monitoring triggers and escalation; custom monitors supply configurable metric or anomaly triggers that could support that pattern.
- [Firetiger joins Cursor](https://feed7.dev/p/firetiger-06hv2bc) — Firetiger’s planned Change Monitors connect rollout checks with diagnosis; Vercel’s monitors provide configurable operational signals, though the account does not establish an automated repair loop.

## Context Map

- Layer: infra
- Domains: data
- Topics: observability, cloud-agents

## Uncertainty

- The feature is for Pro and Enterprise plans with Observability Plus. Scans cost **$0.0035 per GB**; built-in alerts remain included with Observability Plus.

## Agent Instruction

Use this item as source-backed context. Do not invent claims beyond the linked source. If this item conflicts with another source, call out the conflict.