In Query, you first select an event type, then a metric from that event type. For example, select Function Invocations and Active CPU Time to query the CPU time used by Vercel Functions.
The metric picker displays only the event types and metrics available to your team. The following tables use the labels shown in the picker for current event types. Deprecated event types may also appear for historical data.
Count, External Rewrite Connect Time, External Rewrite DNS Time, Fast Data Transfer (Incoming), Fast Data Transfer (Outgoing), Fast Data Transfer (Total), Routing CPU Duration
Count, Duration (ms), Active CPU Time, Duration (Gb-hrs), Time to First Byte, Incoming Fast Origin Transfer, Outgoing Fast Origin Transfer, Total Fast Origin Transfer, Peak Memory, Provisioned Memory
Middleware Invocations
Count, Duration, Active CPU Time, Time to First Byte, Incoming Fast Origin Transfer, Outgoing Fast Origin Transfer, Total Fast Origin Transfer
External APIs
Count, Duration, Transfer Bytes
Queue Actions
Count, Messages Sent, Messages Received, Messages Deleted, Notifications, Visibility Changes, Message Age When Received, Redeliveries, Retry Depth
The aggregation determines how Query combines the selected metric's values. The aggregation picker displays only the options supported by the selected metric.
Aggregation
Description
Count
The number of data points emitted for the selected custom metric. For built-in event types, select the Count metric and the Sum aggregation instead.
Sum
The total of the metric values.
Average
The arithmetic mean of the metric values.
Min
The smallest metric value.
Max
The largest metric value.
P50
The value below which 50% of the metric values fall.
P75
The value below which 75% of the metric values fall.
P90
The value below which 90% of the metric values fall.
P95
The value below which 95% of the metric values fall.
P99
The value below which 99% of the metric values fall.
Std Dev
The standard deviation of the metric values.
Per Second
The metric value expressed as a rate per second.
Percent
Each group as a percentage of the ungrouped total. Values excluded by the filter are also excluded from the total.
Unique
The number of distinct values. Query uses this aggregation for the Visitors metrics.
Aggregations are calculated within each point on the chart (hourly, daily, etc) and also across the entire query window.
The filter bar defines the conditions to filter your query data. It only fetches data that meets a specified condition based on several fields and operators:
The Group By clause calculates statistics for each combination of field values. Each group is displayed as a separate color in the chart view, and has a separate row in the table view.
For example, grouping by Request Hostname and HTTP Status displays data for each combination of hostname and status code.
The available fields depend on the selected event type. The following fields are common across one or more event types:
Field Name
Description
Request Hostname
Group by the request's domains and subdomains
Project
Group by the request's project
Deployment ID
Group by the request's deployment ID
HTTP Status
Group by the request's HTTP response code
Route
The mapped path used by the request. For example, if you have a dynamic route like /blog/[slug] and a blog post is /blog/my-blog-post, the route is /blog/[slug]
Request Path
The path used by the request. For example, if you have a dynamic route like /blog/[slug] and a blog post is /blog/my-blog-post, the request path is /blog/my-blog-post
Group by the action taken by the Vercel Firewall, including allow, bypass, challenge, challenge-solved, challenge-failed, deny, log, rate_limit, and redirect
WAF Rule ID
Group by the firewall rule ID
Skew Protection
When active, the request would have been subject to version skew but was protected, otherwise inactive.
From the Vercel docs graph (built 2026-09-15T06:10:09.927Z), spanning vercel.com docs + KB, nextjs.org, ai-sdk.dev, and other Vercel documentation sites. Full graph as JSON: https://vercel.com/docs/graph.json
Semantically closest pages
Monitoring Reference — This reference covers the clauses, fields, and variables used to create a Monitoring query.
Query Web Analytics with the API — Learn how Web Analytics concepts map to API queries for custom reports, dashboards, and insights.
Query — Query and visualize your Vercel usage, traffic, and more in observability.