Legacy Metrics
Learn about Bandwidth, Requests, Serverless Function Invocations, and Serverless Function Execution metrics.Bandwidth is the amount of data your deployments have sent or received. This chart includes traffic for both preview and production deployments.
You are not billed for bandwidth usage on blocked or paused deployments.
The total traffic of your projects is the sum of the outgoing and incoming bandwidth.
- Outgoing: Outgoing bandwidth measures the amount of data that your deployments have sent to your users. Data used by ISR and the responses from the Edge Network and Serverless Functions count as outgoing bandwidth
- Incoming: Incoming bandwidth measures the amount of data that your deployments have received from your users
An example of incoming bandwidth would be page views requested by the browser. All requests sent to the Edge Network and Serverless Functions are collected as incoming bandwidth.
Incoming bandwidth is usually much smaller than outgoing bandwidth for website projects.
Requests are the number of requests made to your deployments. This chart includes traffic for both preview and production deployments.
Requests can be filtered by:
- Ratio: The ratio of requests that are cached and uncached by the Edge Network
- Projects: The projects that the requests are made to
Serverless Function Invocations are the number of times your Serverless Functions have receive a request, excluding cache hits.
Serverless Function Invocations can be filtered by:
- Ratio: The ratio of invocations that are Successful, Errored, or Timed out
- Projects: The projects that the invocations are made to
Serverless Function Execution is the amount of time your Serverless Functions have spent computing resources.
Serverless Function Execution can be filtered by:
- Ratio: The ratio of execution time that is Completed, Errored, or Timed out
- Projects: The projects that the execution time is spent on
Was this helpful?