What is a subrequest?
With a no-op Worker (a Worker that simply proxies traffic by passing on the original client request to the origin and proxying the response) running on a particular route, the request to the origin is counted as a “subrequest”, separate from initial client to edge request. Thus, unless the Worker responds with a static response and never hits an origin, the eyeball → edge request, and edge → origin request will each be counted separately towards the request or bandwidth count in Analytics.
In the dashboard, the numbers in zone analytics reflect eyeball facing traffic. That is, the number of requests shown in zone analytics (under the Analytics tabs in the dashboard) is the number of requests that were served to the client. Similarly, the bandwidth is counted based on bandwidth that is sent to the client, and tatus codes reflect the status codes that were served back to the client (so if a subrequest received a 500, but you respond with a 200, a 200 will be shown in the status codes breakdown).
For a breakdown of subrequest traffic (origin facing traffic), you may go to the Workers tab in the dashboard. Under the Workers tab, below the Service Workers panel, you will see a Subrequests breakdown by count, bandwidth and status codes. This will help you spot and debug errors at your origin (such as spikes in 500s), and identify your cache-hit ratio to help you understand traffic going to your origin.
Why did my traffic suddenly drop?
When we initially launched Cloudflare Workers, we included both requests and subrequests in zone analytics. To help you understand the actual traffic to your site or APIs, we have removed the subrequest traffic, and only show client facing (eyeball traffiic) in zone analytics. You may find analytics for your subrequests under the Workers tab.
Why don’t I see any analytics in the Workers tab?
- If you are not currently using Workers (don’t have Workers deployed on any routes or filters), we will not have any information to show you.
- If your Worker sends a static response back to the client without ever calling fetch() to an origin, you are not making any subrequests, thus, all traffic will be shown in zone Analytics
Why can’t I see any subrequests prior to 2018-08-16 22:00 UTC?
While you can’t get subrequest information prior to this date, you will still be able to get this infromation about the client facing traffic in the Analytics tab. If you are on our Enterprise plan, you may still get data for previous dates from our Enterprise Log Share.
Will this impact billing?
No, billing for Workers is based on requests that go through a Worker.
Why am I seeing such a high cache hit ratio?
Requests served by a Worker will always show as cached. For an accurate cache hit ratio on subrequests, see analytics under Workers.