Usage Dashboard Brings Team Resource Metrics Into Focus

Pro and Enterprise users now get a dedicated view of how their teams consume platform resources. The new Usage overview presents metrics for each project and Serverless Function across three categories: Networking, Functions, and Builds. The data appears in easy-to-read charts with automated insights embedded directly into each section.

Networking: Bandwidth and Requests

Two primary views comprise the Networking category. The Bandwidth section separates incoming traffic from outgoing data sent by your Serverless Functions and Edge Network. This distinction helps identify whether functions are transmitting or retrieving significant amounts of data, which is often a signal worth investigating.

The Requests section splits traffic between cached and non-cached hits. Seeing how much of your traffic is served from cache at a glance makes it simpler to gauge site performance. Heavier cache usage typically translates to faster response times. For details on improving cache hit rates, the Edge Caching documentation covers the mechanics.

Function Performance Metrics

The Functions category focuses on how your serverless workloads are behaving under real traffic. Invocations and Executions sections report on two things: how often functions get called and how long they take to finish. More importantly, these views surface two critical failure states:

  • Errored: shows requests that failed and the run duration before the failure occurred.
  • Timeout: counts how many times a function hit its execution timeout limit.

The Throttled section tracks functions that were blocked by concurrency limits. In that situation, Vercel attempts to scale up a function, but if traffic spikes beyond what a deployment can handle, additional instances cannot be created and requests get throttled. Keeping all three of these numbers as close to zero as possible is the operational target.

Build Pipeline Visibility

Build tracking in the dashboard shows how long deployments stayed in the queue, how much time the builds themselves consumed, and the total build count per project. This section is meant for optimizing the path to production. If builds repeatedly sit in queue for extended periods, increasing your plan to access more concurrent builds can shorten the time between commit and deploy.

Insights, Defaults, and Access

Prior to this release, tracking usage meant exporting CSVs and doing your own visualization, which slowed down the optimization loop. The overview consolidates the visual data into a single location and also evaluates the metrics for improvement opportunities. When the dashboard identifies a potential fix, it surfaces the suggestion in the Insights area of the relevant section.

Usage overview is enabled by default and included with Pro and Enterprise subscriptions. Legacy Team plan accounts will see an upgrade prompt to one of the newer tiers before the feature becomes available.