Agent skill · security · jeremylongshore
logging-api-requests
Monitor and log API requests with correlation IDs, performance metrics,
Why this skill is useful
Adds executable middleware scripts for structured API logging, correlation ID management, and PII redaction that extend the AI's capabilities.
What it needs
Requires logback, pino, structlog, winston installed locally. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
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 mask sensitive fields (passwords, tokens, SSNs, email addresses) in logged request/response bodies using configurable field-path patterns. 5. Implement log levels per context: info for successful requests, warn for 4xx client errors, error for 5xx server errors with stack traces, and debug for request/response bodies (development only). 6. Configure response body logging for error responses only (4xx/5xx), capturing the error payload for debugging while skipping successful response bodies to reduce log volume. 7. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/logging-api-requests