OBSERVABILITY Signal 473
Custom metrics are now supported in Vercel Observability
↗
Vercel Functions can now emit user-defined metrics through a metric() helper in the @vercel/functions package, and the values flow into Vercel Observability's query builder, Notebooks, and vc metrics CLI alongside Vercel's built-in telemetry.
This gives Vercel-hosted code a first-party channel for application-level signals like database query latency or business events without standing up a separate metrics pipeline. Vercel auto-tags each emit with the source deployment and function region, so the common dimensions are filled in for you. The trade-off is that custom metrics are billed as observability events and gated to Pro and Enterprise plans with Observability Plus.
Written by elseif from the cluster below · every claim links back to a sourceThe three things worth knowing
The metric() function in @vercel/functions records a named value with optional attributes, e.g. metric("database.query_ms", 120, { table, db }), and attributes are what the query layer slices and groups by.
Emitted values appear in Vercel Observability's query builder, Notebooks, and the vc metrics CLI command, sitting alongside the platform's built-in telemetry rather than in a separate system.
Vercel automatically adds the source deployment and function region as attributes, and custom metrics are billed as observability events on Pro and Enterprise plans with Observability Plus.
THE CLUSTER