Common observability
Skill ComeOnOliver/skillshub/skills/HoangNguyen0403/agent-skills-standard/common-observability
🧠The right skill, one API call. AI agent skills registry with token-efficient skill resolution. 5,000+ skills from 500+ top repos.
npx -y skills add ComeOnOliver/skillshub --skill common-observabilityAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
What its author says it does
Copied from the file, not written here
Standards for structured logging, distributed tracing, and metrics. (triggers: **/*.service.ts, **/*.handler.ts, **/*.middleware.ts, **/*.interceptor.ts, **/*.go, **/*.java, **/*.kt, **/*.py, logging, tracing, metrics, opentelemetry, observability, slo)
SKILL.md
1.2 KB, as published. Nobody here has run it
Common Observability Standards
Priority: P1 (OPERATIONAL)
📋 Logging & Tracing
- JSON Logs: Always emit JSON structured logs. Never plain-text in prod.
- Correlation: Extract
X-Request-Idortraceparent. Attach to async context. - Tracing: Use OpenTelemetry. Propagate W3C
traceparent. - Spans: Name spans like
<HTTP_METHOD> <route>(GET /users/:id).
📊 Metrics
- Required: Request rate, Error rate, Latency histogram (p50/p95/p99), Saturation.
- SLOs: Alert on SLO burn rates, not raw threshold spikes.
🚫 Anti-Patterns
- Console.log: Do not use in prod; use a structured logger (
pino,zap). - PII in Logs: Never log tokens, passwords, or full request bodies.
- Dynamic Span Names:
GET /users/123causes cardinality explosion. UseGET /users/:id. - Missing Cleanup: Always end tracing spans.