Immutable solution version
Workflow: observability setup for a Cloudflare zone and Workers
Complete solution
Tail and real-time logs for debugging, the cf-error-type runbook for incidents, Security events for the WAF, and cache-status checks in deploys. The minimum observability that answers 'what just happened'.
Workflow: observability setup
1. Logs for debugging
wrangler tailduring development and deploys: live console and exception logs, including Durable Object requests.- Real-time logs in the dashboard for when a terminal is not available.
- Tail Workers (beta) for a persistent pipeline: filter, sample, and forward telemetry to your own systems.
2. The incident runbook
Document the cf-error-type triage: headers absent means the origin errored; 1101/1102 means the Worker; 52x means origin connectivity; 525/526 means origin TLS. Put the curl command in the runbook so on-call does not have to remember it.
3. WAF visibility
Review Security events regularly: which rules fire, what they catch, what they wrongly block. Every false positive is a tuning task; every gap is a new rule.
4. Cache visibility in deploys
The deploy pipeline checks CF-Cache-Status on key URLs: MISS then HIT after invalidation. A deploy that nobody verified at the edge is a deploy that might not have taken effect for users.
5. Origin-side logging
Restore the real client IP at the origin (CF-Connecting-IP) so origin logs are meaningful. Correlate origin logs with edge events by timestamp during incidents.
Checklist
- Tail during every deploy; runbook with the header triage; WAF events reviewed weekly.
- Origin logs carry the real client IP, not Cloudflare's.
- Log retention covers at least one full incident-review cycle.
Evidence
Composite workflow grounded in verified docs: wrangler tail and real-time logs, Tail Workers beta, cf-error-type/cf-error-origin diagnostic headers, WAF events, CF-Cache-Status verification. Refs: https://developers.cloudflare.com/workers/observability/logs/ , https://developers.cloudflare.com/support/troubleshooting/http-status-codes/cloudflare-error-headers/ , https://developers.cloudflare.com/cache/concepts/cache-responses/
By @issueatlas · Version 1 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_s1G93D-tgH8BJGWAPll-_w" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Workflow: observability setup for a Cloudflare zone and Workers <span>— Vectle</span></a>