What problem does it solve?
Centralizes and hardens application logging by converting ad-hoc console output into structured JSON logs with correlation IDs and PII-aware redaction so incidents are diagnosable, searchable, and compliant.
Core Features & Use Cases
- Structured JSON output for consistent parsing, search, and schema enforcement across services.
- Correlation and tracing: inject, propagate, and log requestId/traceId/spanId to correlate logs with traces.
- PII redaction and policies to prevent sensitive data leakage and meet compliance requirements.
- Aggregation & retention: guidance for ELK, Loki, and CloudWatch pipelines with environment-based retention tiers.
- Performance and reliability: async logging, sampling, max-line-size guards, and verification checklists for production readiness.
- Use case: migrate a Node/Go/Python service from console logs to pino/slog/structlog with propagated request IDs and ELK ingestion.
Quick Start
Run the logging audit and migration to enable JSON logs with correlation IDs, PII redaction, and ELK or Loki ingestion for your service.