Agent skill · data analytics · secondsky
cloudflare-workers-observability
Cloudflare Workers observability with logging, Analytics Engine, Tail Workers, metrics, and alerting. Use for monitoring, debugging, tracing, or encountering log parsing, metric aggregation, alert configuration errors.
Why this skill is useful
Provides specific logging patterns and configuration for Cloudflare Workers that enhance observability and error prevention.
What it needs
About 4k tokens when loaded. Last updated 2026-08-06. 204 stars on the source repository.
What this skill does
Cloudflare Workers Observability Production-grade observability for Cloudflare Workers: logging, metrics, tracing, and alerting. Quick Start Critical Rules 1. Always use structured JSON logging - Plain text logs are hard to parse and aggregate 2. Include request context - Request ID, method, path in every log entry 3. Never log sensitive data - Redact tokens, passwords, PII from logs 4. Use appropriate log levels - ERROR for failures, WARN for recoverable issues, INFO for operations 5. Sample high-volume logs - Use 1-10% sampling for request logs in production Observability Components Component Purpose When to Use ----------- --------- ------------- console.log Basic logging Development, debugging Tail Workers Real-time log streaming Production log aggregation Analytics Engine Custom metrics/analytics Business metrics, performance tracking Logpush Log export to external services Long-term storage, compliance Workers Trace Events Distributed tracing Request flow debugging Top 8 Errors Prevented Error Symptom Prevention ------- --------- ------------ Logs not appearing No output in dashboard Enable "Standard" logging in wrangler.jsonc Log truncation Messages cut off at 128KB Chunk large payloads, use sampling Tail Worker not receiving No events processed Check binding name matches wrangler.jsonc Analytics Engine write fails Data not recorded Verify AE binding, check blobs format PII in logs Security/compliance violation Implement redaction middleware Missing request context Can't correlate logs Add requestId to all log entries Log volume explosion High costs, noise Implement sampling for high-frequency events Alerting gaps Incidents not detected Configure monitors for error rate thresholds Logging Configuration wrangler.jsonc: Structured Logging Pattern Analytics Engine Usage Tail Worker Pattern When to Load References Load specific references based on the task: Setting up logging? → Load references/logging.md for structured logging patterns, log levels, redaction Bui …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills secondsky/cloudflare-workers-observability