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.
91
88%
Does it follow best practices?
Impact
97%
1.19xAverage score across 3 eval scenarios
Passed
No known issues
Structured logging with redaction and sampling
JSON structured logs
100%
100%
requestId in every log
100%
100%
cf-ray header usage
100%
100%
Password redaction
100%
100%
Token/auth redaction
100%
100%
Error level for failures
62%
62%
Warn level for recoverable
100%
100%
Timestamp in log entry
100%
100%
Log sampling implemented
0%
100%
Errors/warns bypass sampling
0%
100%
observability in wrangler
100%
100%
Analytics Engine metrics tracking
writeDataPoint used
100%
100%
blobs for categorical data
100%
100%
doubles for numeric data
100%
100%
indexes used for filtering
100%
100%
ctx.waitUntil for writes
25%
100%
Consistent schema
100%
100%
Error path instrumented
62%
100%
ANALYTICS binding in wrangler
0%
100%
Schema documented
100%
100%
Queries use blob/double names
100%
100%
Response time recorded
100%
100%
Tail Worker alerting pipeline
tail_consumers in producer
100%
100%
Service name matches
100%
100%
Tail Worker exports tail()
100%
100%
Filters errors only
100%
100%
Alert cooldown logic
100%
100%
Cooldown duration >= 5 min
100%
100%
Alert deduplication key
0%
40%
Slack alert with context
100%
100%
KV for state storage
100%
100%
KV binding in wrangler
100%
100%
No alert on ok outcome
100%
100%
90d6bd7
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.