☁️ DevOps & Cloud · Observability
Adopt structured logging that answers questions
JSON logs with trace correlation and disciplined fields you can actually query at 3am.
foundation~25 minDevOps EngineersSREsCloud Architects
Steps
- 1Log JSON with timestamp, level, service, route, request_id, user_id
- 2Propagate trace IDs across services and into log lines
- 3Reserve ERROR for things needing action; INFO is default heartbeat
- 4Never log secrets or PII; enforce with lint rules and sampling reviews
- 5Sample high-volume debug logs; keep 100% of errors
- 6Practice one query drill: 'find all errors for this user yesterday'
Common Pitfalls
- ▲String-interpolated logs unsearchable in aggregators
- ▲Stack traces swallowed into single-line messages
Commands
Install with skills CLI
$ npx skills add aniruddhaadak80/skills --skill observability-structured-loggingInstall globally
$ npx skills add aniruddhaadak80/skills --skill observability-structured-logging -gTags
#logging#debugging#devops-cloud#observability