Skip to content
All tool news

Tool desk · Updated daily

Tool news·Vercel·

Vercel Adds Custom metrics to Observability for App-Level Monitoring.

Vercel adds Custom metrics to Observability, letting teams track application-specific performance and business events from Functions.

CW

Create With tool desk

1 source checked · 3 min read · 3 sections

ShareLinkedIn
Vercel Adds Custom metrics to Observability for App-Level Monitoring

Vercel is expanding its built-in monitoring beyond infrastructure signals. With Custom metrics, developers can now emit application-specific measurements from Vercel Functions, then analyze that data alongside the platform’s existing observability information.

The feature, detailed in an official changelog entry published August 20, 2026, gives teams a native way to track values such as database latency, transaction activity and events generated by custom business logic. Previously, those measurements often required a separate analytics or monitoring service.

Custom metrics arrive as Vercel also broadens its production diagnostics, following the addition of always-on tracing for production and preview traffic. Together, the releases push Vercel Observability toward a more complete view of how applications behave, not just how the underlying deployment performs.

How Custom Metrics Work

Developers record a metric using the metric() function from the @vercel/functions package. The function accepts a metric name, a numeric value and optional attributes that can later be used to filter or group the results.

Vercel’s example measures the duration of a database query:

import { metric } from "@vercel/functions";

metric("database.query_ms", 120, {
  table: "my-table",
  db: "my-database"
});

In this case, the application records a value of 120 for database.query_ms, while identifying the relevant table and database. A team could use the same approach to measure checkout processing time, jobs completed, AI inference duration or another numerical signal relevant to its application.

Vercel automatically attaches contextual attributes, including the source deployment and the region where the function ran. That reduces the need for developers to add routine infrastructure metadata themselves. It also makes it possible to investigate whether an application-level change is isolated to a particular deployment or location.

Once collected, the measurements are available through three parts of Vercel Observability:

  • Query builder: Metrics can be filtered, grouped and aggregated interactively.
  • Notebooks: Teams can turn queries into dashboards and share the resulting analysis.
  • CLI: Developers can retrieve metrics from a terminal using the vc metrics command.

The combination matters for smaller teams. A developer can investigate an incident from the command line, while a product or operations team can follow the same underlying signal through a shared notebook.

What It Changes for Builders

Default platform metrics are useful for identifying broad technical problems, but they do not necessarily explain what an application was doing when the issue occurred. A latency spike, for example, becomes more actionable when it can be compared with a custom measurement for database query time or another workload-specific operation.

Business events can also sit closer to operational data. A SaaS company could record the volume of completed imports, while a marketplace might measure the number of transactions processed by a function. Because attributes can be attached to each measurement, teams can segment results without creating a separate metric name for every variation.

There are cost and access considerations. Vercel says Custom metrics are available to Pro and Enterprise customers using Observability Plus. The measurements are billed as observability events, so teams generating high-volume metrics will need to account for that event usage when deciding what to instrument.

The announcement does not specify separate pricing, retention periods or event limits for Custom metrics. Teams evaluating the feature should therefore consult their current Observability Plus terms before instrumenting frequently executed functions.

Frequently asked questions

What is Vercel Custom metrics?

Custom metrics is a Vercel Observability feature that lets developers record application-specific numerical measurements from Vercel Functions. Those measurements can include attributes for filtering and grouping, and Vercel automatically adds context such as the deployment and function region.

Which Vercel plans support Custom metrics?

Custom metrics are available on Pro and Enterprise plans with Observability Plus. Vercel says the emitted measurements are billed as observability events.

Where can teams analyze Custom metrics?

Custom metrics can be analyzed in Vercel Observability’s query builder and used in shareable Notebooks. Developers can also query them from the command line with vc metrics.

Sources

1 checked

How we cover tool news: Create With's tool desk drafts these reports with AI from the sources listed above and checks them against those sources before publishing.

Worth passing on?

ShareLinkedIn

Go deeper on Vercel

Related reading, watching and going.

Everything on Vercel →

The briefing

19 May 2026

How to Migrate Your App from Lovable to Claude Code in 2025

Step-by-step guide to migrating your Lovable app to Claude Code. Learn how to move from Lovable's managed platform to a stack you own and control.

Read →

The briefing

10 Feb 2026

OpenClaw Review: 2 Weeks With This AI Agent

Honest 2-week review of OpenClaw — an autonomous AI agent powered by Claude. We test setup, safety, autonomy, and real value to see if it's worth using.

Read →
34 min

Podcast

My Daughter Built a Website Business, Claude Design First Look & Going All-In on Cloudflare

James and Kieran discuss practical AI-powered development through real-world examples, including a seven-year-old building a website business with Claude Code voice mode, Anthropic's new Claude Design tool, API security challenges in the AI agent era, and Cloudflare's expanding AI infrastructure offerings. The episode covers hands-on experiences with vibe coding, emerging design tools, and the evolving landscape of AI-assisted development.

Watch now ↗

Podcast

53. Why Your Vibe Code Needs Tests, Ditching SaaS & AI Agents That Work While You Sleep

James and Kieran discuss the practical realities of building AI-powered software, emphasizing the importance of testing in vibe-coded applications, exploring alternatives to traditional SaaS tools, and implementing autonomous AI agents for business operations. The episode covers technical topics like Convex databases, app store bottlenecks from AI-generated submissions, and using OpenClaw as a marketing automation agent.

Watch now ↗
38 min

Podcast

52. Your AI Co-Founder: OpenClaw, Manus & the Zero-Person Business

In this Create With podcast episode, James and Kieran are joined by Matt Roberts from Happy Operators for an in-depth discussion on using autonomous AI agents in production. The conversation covers practical experiences with OpenClaw, security considerations, comparison with emerging tools like Manus, and the broader shift toward AI-assisted development. They also discuss the VibeCoding Olympics results, Bubble's new AI capabilities, and research on Claude.MD file effectiveness.

Watch now ↗

Latest tool news

What else changed this week.

All tool news
VercelDigest

What Vercel Shipped in Late October

Vercel shipped quicker static deployments, four AI Gateway models, more free domain choices and new CLI controls in late October. The changes cover developers testing sites…

Vercel

Vercel Adds Submit_feedback to Its MCP

submitfeedback is a new Vercel MCP tool that lets agents and harnesses send bug reports, friction reports and feature requests directly to the Vercel team. Feedback can include…

The Create With Briefing

Don't watch forty changelogs. Read one email.

Every Tuesday: the tool changes worth knowing, real business use cases, and what's on near you. Free, unsubscribe any time.