> ## Documentation Index
> Fetch the complete documentation index at: https://bunny.net/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Edge Scripting Statistics

> Monitor requests, CPU time, wall time, memory, subrequests, errors, and release performance for your Edge Script.

The **Statistics** tab shows how your script performs in production. Use it to track traffic and resource usage, spot errors, and compare releases after a deployment.

To open it, select your script and then select **Statistics** in the navigation pane.

## Filter the data

Every panel on the page uses the filters at the top:

* **Timeframe**: The date range to show.
* **Granularity**: The size of each data point on the charts, such as hourly.
* **Release**: Show data for every release, or for a single [deployment](https://bunny.net/docs/scripting/deployments.md).
* **Region**: Show data for every region, or for a single [region](https://bunny.net/docs/scripting/regions.md).

Select the refresh button on the right to load the latest data.

## Requests and CPU time

![Requests served and CPU time consumed charts](https://mintcdn.com/bunnynet-cb9733c2/WxbfcaOxWipkuEU6/images/scripting/statistics-requests-cpu-time.png?fit=max\&auto=format\&n=WxbfcaOxWipkuEU6\&q=85\&s=30b4c9a583180e788a0315adfe09575d)

* **Requests served**: The total number of requests your script handled in the timeframe.
* **CPU time consumed**: The total CPU time your script used to run your code. Time spent waiting on network calls doesn't count. CPU time is the basis for [billing](https://bunny.net/docs/scripting/pricing.md).

## Wall time and memory usage

![Wall time and memory usage charts](https://mintcdn.com/bunnynet-cb9733c2/WxbfcaOxWipkuEU6/images/scripting/statistics-wall-time-memory.png?fit=max\&auto=format\&n=WxbfcaOxWipkuEU6\&q=85\&s=4f3566909d4fc196d094996085a0fca7)

* **Wall time**: The average time a request takes from start to finish, including time spent waiting on subrequests and other I/O. A high wall time with a low CPU time usually means that your script is waiting on a slow origin.
* **Memory usage**: The average memory used by each isolate running your script. Compare this value with the [memory limit](https://bunny.net/docs/scripting/limits.md).

## Subrequests

The **Subrequests** table lists every origin your script called with `fetch()`. For each origin, it shows the number of requests, a breakdown by status code class (`2XX`, `3XX`, `4XX`, `5XX`), and the average request duration. Use the search box to find an origin.

Use it to find the upstream service that is slow or returning errors.

## Errors by request status

![Errors by request status chart](https://mintcdn.com/bunnynet-cb9733c2/WxbfcaOxWipkuEU6/images/scripting/statistics-errors.png?fit=max\&auto=format\&n=WxbfcaOxWipkuEU6\&q=85\&s=75471155d49889d27bcc9e3513307dbf)

This panel counts the requests that failed, grouped by cause:

| Status | Meaning |
| - | - |
| Exceeded memory | The script went over the [memory limit](https://bunny.net/docs/scripting/limits.md). |
| Exceeded CPU time limits | The script went over the [CPU time limit](https://bunny.net/docs/scripting/limits.md#cpu-time). |
| Uncaught exception | The script threw an error that it didn't catch. |
| Timeout | The script did not finish in time. |
| Internal | An error happened in the platform. |

To find out what caused an uncaught exception, look at the [logs](https://bunny.net/docs/scripting/logs.md) for the same timeframe.

## Release comparison

The **Release comparison** panel shows how each release performed. When more than one release served requests in the timeframe, you can compare them side by side. Use this panel after a deployment to check the new release's CPU time, wall time, and memory against the previous release.

The table shows these values for each release:

* **Release**: The deployment ID.
* **Requests**: The number of requests the release served.
* **CPU time**: The total CPU time the release used.
* **CPU time / request**: The average CPU time for each request.
* **Avg wall time / request**: The average wall time for each request.
* **Avg memory / isolate**: The average memory used per isolate.
* **Cold start rate**: The percentage of requests that had to start a new isolate.
* **Startup time**: The average time to start the script on a cold start.

If a new release performs worse, you can [publish a previous deployment](https://bunny.net/docs/scripting/deployments.md#publishing-previous-deployments) to roll back.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.