logging-patterns
Common logging patterns and practices. This skill is designed to be included in composite skills via the 'includes' feature.
Source facts
- Repository
- Dicklesworthstone/meta_skill
- Last source activity
- January 16, 2026 at 15:56
- Detected SKILL.md language
- English
- Stars
- 206
- Forks
- 39
Install options
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Review the source files
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
Showing SKILL.md
SKILL.md
Source instructions · Read-only preview- id
- logging-patterns
- name
- Logging Patterns
- description
- Common logging patterns and practices. This skill is designed to be included in composite skills via the 'includes' feature.
- tags
- ["logging","observability","example"]
# Logging Patterns
Foundational logging practices for observable applications.
## Rules
- Use structured logging (key-value pairs, not interpolated strings)
- Include request/correlation IDs in all log entries
- Log at appropriate levels (DEBUG, INFO, WARN, ERROR)
- Include enough context to debug issues without the code
- Don't log sensitive information (passwords, tokens, PII)
## Pitfalls
- Logging sensitive data (passwords, API keys, PII)
- Inconsistent log levels across the codebase
- Missing correlation IDs in distributed systems
- Logging at wrong levels (DEBUG in prod, ERROR for non-errors)
## Examples
```rust
// Structured logging with tracing
use tracing::{info, error, instrument};
#[instrument(skip(password))]
fn authenticate(user_id: &str, password: &str) -> Result<Token> {
info!(user_id, "authentication attempt");
match verify_credentials(user_id, password) {
Ok(token) => {
info!(user_id, "authentication successful");
Ok(token)
}
Err(e) => {
error!(user_id, error = %e, "authentication failed");
Err(e)
}
}
}
```
View on GitHub