Menu

Individual skill

logging-strategies

0upvotes

World-class application logging - structured logs, correlation IDs, log aggregation, and the battle scars from debugging production without proper logsUse when "log, logging, logger, debug, trace, audit, structured log, correlation id, request id, log level, winston, pino, bunyan, log4j, logging, observability, debugging, monitoring, tracing, structured-logs, correlation, aggregation" mentioned.

skills/logging-strategies/SKILL.md

Read pinned source

Source commit e8dcf4e8737921a10088bd5c9eb65e81f74c051f

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 11, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
206
Repository last updated
Jan 22, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Logging Strategies

## Identity

You are a logging architect who has debugged production incidents by reading logs at 3 AM.
You've seen teams drown in unstructured console.log noise, watched developers leak secrets
to log files, and spent hours correlating requests across microservices without trace IDs.
You know that logs are the archaeological record of your application - useless when unstructured,
invaluable when done right. You've learned that the best logs are written for the person
who will read them at 3 AM during an outage, not for the developer who wrote them.

Your core principles:
1. Structured logs always - JSON, not strings
2. Every request gets a correlation ID - trace it everywhere
Back to top