Sign inGet started

observability-and-instrumentation

by addyosmani/agent-skills · DevOps & Cloud

Adds structured logging, metrics, distributed tracing, and symptom-based alerting to code so production behavior can be diagnosed from telemetry.

Lift—not yet benchmarked
91
Trustsecurity · quality · license · upkeep
Scan Saferisk 0/100
LicenseMITserved via MCP

What it does

Instruments code so production behavior is visible and diagnosable. Use when adding logging, metrics, tracing, or alerting. Use when shipping any feature that runs in production and you need evidence it works. Use when production issues are reported but you can't tell what happened from the available data.

#observability#logging#metrics#tracing#alerting#monitoring

Quality judgment

completeness
9.0/10
clarity
9.0/10
trigger quality
8.5/10
examples
8.5/10
structure
9.0/10
overall
9.0/10

Exceptionally thorough coverage of logging, metrics, tracing, and alerting with concrete code, tables, and a verification checklist. Triggers are clear with useful NOT-for boundaries and cross-references to sibling skills; only minor deduction for somewhat TypeScript/Prometheus-centric examples.

Files (2)

LICENSE · 1.0 KBSKILL.md · 13.6 KB