forge-logging

Structured JSON logging converts unstructured application logs into parseable JSON objects, attaching request_id and trace_id to tie logs to a single request path across services. This ensures each log line is correlatable, correctly leveled, and safe for aggregation pipelines.

Redact secrets at the logger so Authorization tokens and credential-like strings never reach storage. This structured logging discipline prevents secret-leaking application logs by enforcing source redaction before logs are written to aggregation pipelines.

Enforcing required fields like timestamp, level, message, and service alongside stable message strings ensures reliable JSON log events for oncall debugging. Environment-controlled log levels maintain correct severity boundaries for incident response.

Structured logging works for HTTP services, background jobs, and scheduled tasks by applying standardized logging discipline. Each log line becomes a correlatable JSON object suitable for filtering, alerting, and incident debugging across different execution contexts.

Separating audit logs from regular application logs ensures distinct retention policies and security handling. This structured logging discipline creates reliable JSON log events specifically for audits, keeping them isolated from general incident debugging logs.

Enforce verifier-enforced discipline against unsafe patterns like console.log or templated messages to ensure logs support aggregation pipelines. Standardized structured JSON logging replaces unstructured outputs with parseable, correlatable JSON log events.