logging-api-requests

# Logging API Requests ## Overview Implement structured API request logging with correlation IDs, performance timing, security audit trails, and PII redaction. Capture request/response metadata in JSON format suitable for aggregation in ELK Stack, Loki, or CloudWatch Logs, enabling debugging, performance analysis, and compliance auditing across distributed services. ## Prerequisites - Structured logging library: Pino or Winston (Node.js), structlog (Python), Logback with JSON encoder (Java) - Log aggregation system: ELK Stack (Elasticsearch, Logstash, Kibana), Grafana Loki, or CloudWatch Logs - Correlation ID propagation mechanism (middleware-injected or from incoming `X-Request-ID` header) - PII data classification for the API domain (which fields contain personal data requiring redaction) - Log retention and rotation policy defined per compliance requirements ## Instructions 1. Examine existing logging configuration using Grep and Read to identify current log format, output destinations, and any structured logging already in place. 2. Implement request logging middleware that captures: timestamp (ISO 8601), correlation ID, HTTP method, URL path (without query string PII), status code, response time (ms), request size, response size, and client IP. 3. Generate a unique correlation ID (`X-Request-ID`) for each request if not provided by the caller, and propagate it to all downstream service calls and log entries within the request scope. 4. Add PII redaction rules that ...