Busy Cloudflare Workers logging 100% of requests to Workers Logs
CloudflareCost optimizationFree planSeverity: medium
cloudflare.worker-scriptWorkers with Workers Logs enabled, a head sampling rate of 1 (every request logged) and at least 10 million requests in the last 7 days
What LeftSize checks
Find busy Workers that log every invocation: Workers Logs enabled with a head sampling rate of 1 (100%) and at least 10 million requests in the last 7 days.
Why it matters
Resources like this keep billing every hour while delivering little or no value, and nobody notices until the invoice arrives.
What you get in the issue
LeftSize runs this check from a scheduled GitHub Action with a read-only Cloudflare API token that stays on your runner, and opens one issue per Cloudflare account in GitHub or Jira, updated on every scan. The issue includes:
- The affected resources, grouped per Cloudflare account
- An estimated monthly cost where pricing data is available
- Background on why it was flagged and when it is a false positive
- Step-by-step remediation with safety checks
- Ready-to-run fix scripts (Cloudflare API, Wrangler or Terraform where available)
- Cost and operational impact of fixing it
- Alternative approaches and their trade-offs
- Snooze, ignore or report a finding with a comment on the issue
Install LeftSizeIncluded in the Free plan.
See the @leftsize commands,how LeftSize works andhow to set it up.