Metrics and analytics
There are two graphical sources of information about your Workers traffic at a given time: Workers Metrics and zone-based Workers analytics. Workers metrics can help you diagnose issues and understand your Workers workloads by showing performance and usage of your Workers. If your Worker runs on a route on a zone, or on a few zones, the Workers tab in the zone can help you understand on a per-zone basis how much traffic your Worker is handling, and how many requests your site is getting.
Workers metrics aggregate request data for an individual Worker script (if your Worker is running across multiple domains, and on workers.dev, metrics will aggregate requests across them). You can click on any Worker to view its metrics in your .
There are two metrics that can help you understand the health of your Worker in a given moment: requests success and error metrics, and invocation statuses.
The first graph shows historical request counts from the Workers runtime broken down into successful requests, errored requests, and subrequests.
- Total: All incoming requests registered by a Worker script. Requests blocked by or other security features will not count.
- Success: Requests that returned a Success or Client Disconnected invocation status.
- Errors: Requests that returned a Script Threw Exception, Exceeded Resources, or Internal Error invocation status — see Invocation Statuses below for a breakdown of where your errors are coming from.
- Subrequests: Requests triggered by calling
fetchfrom within a Worker script. A subrequest that throws an uncaught error will not be counted.
Note: request traffic data may display a "drop off" near the last few minutes displayed in the graph for time ranges less than six hours. This does not reflect a drop in traffic, but a slight delay in aggregation and metrics delivery.
Worker invocation statuses indicate whether a Worker script executed successfully or failed to generate a response in the Workers runtime. Invocation statuses differ from HTTP status codes. In some cases, a Worker script invocation succeeds but does not generate a successful HTTP status because of another error encountered outside of the Workers runtime. Some invocation statuses result in a being returned to the client.
|Invocation status||Definition||Workers error code||GraphQL field|
|Success||Worker script executed successfully|
|Client disconnected||HTTP client (i.e. the browser) disconnected before the request completed|
|Exceeded resources¹||Worker script exceeded runtime limits||1102, 1027|
|Internal error²||Workers runtime encountered an error|
² The Internal Error status may appear when the Workers runtime fails to process a request due to an internal failure in our system. These errors are not caused by any issue with the Worker code nor any resource limit. While requests with Internal Error status are rare, we expect that some may appear during normal operation. These requests are not counted towards usage for billing purposes. If you notice an elevated rate of requests with Internal Error status, please check .
The CPU time chart shows historical CPU time data broken down into relevant quantiles using . You can . In some cases, higher quantiles may appear to exceed without generating invocation errors because of a mechanism in the Workers runtime that allows rollover CPU time for requests below the CPU limit.
The duration chart shows historical per Worker execution. The data is broken down into relevant quantiles, similar to the CPU time chart. You can . Understanding duration on your Worker is especially useful when you are intending to do a significant amount of computation on the Worker itself.
The egress data chart shows the total amount of data sent out of the Worker over the selected time period. The data is broken into
response body to help with understanding when and where the data is being sent out from. If you are sending data to members of the , the values shown in this chart may not align with the usage costs at the end of the month. For more information billing see the .
Worker script metrics can be inspected for up to 3 months in the past in maximum increments of 1 week. The dashboard includes the charts and information described below.
Zone data can be scoped by time range within the last 30 days. The dashboard includes charts and information described below.
This chart shows subrequests — requests triggered by calling
fetch from within a Worker script — broken down by cache status.
- Uncached: requests answered directly by your origin server or other servers responding to subrequests
- Cached: requests answered by Cloudflare’s . As Cloudflare caches more of your content, it accelerates content delivery and reduces load on your origin.
This chart shows historical bandwidth usage for all scripts on a zone broken down by cache status.
This chart shows historical requests for all scripts on a zone broken down by HTTP status code.
This chart shows historical data for all scripts on a zone broken down by successful requests, failed requests, and subrequests. These request types are categorized by HTTP status code where 200-level requests are successful and 400 to 500-level requests are failed.