Structured Logging¶

Stable ID: component.logging
Kind: shared-component
Status: stable
Source: skill/references/shared-components/logging.md

Purpose¶

Provide consistent structured events, context propagation, and redaction without coupling domain logic to one logging vendor.

Use when¶

• Multiple components need consistent fields and correlation identifiers.
• Operational diagnosis depends on machine-readable events.
• Sensitive data must be redacted centrally.

Avoid when¶

• A small command-line tool only needs direct user-facing output.
• The wrapper would hide useful standard logging APIs without adding policy.

Applicability¶

• Languages: any, python, q-kdbplus, cpp, rust, dart-flutter, typescript
• Related entries: workflow.bug-fix.incident-response