Emit one structured wide event per request at service boundaries.
npx skills add https://github.com/jonmumm/skills --skill wide-events-logging
Please help me install this Agent Skill. Skill: wide-events-logging Source: https://github.com/jonmumm/skills/tree/main/wide-events-logging Command: npx skills add https://github.com/jonmumm/skills --skill wide-events-logging
Traditional logging scatters contextual data across many statements, making it hard to correlate incidents and understand a complete request path. Wide Events offer a single, highly-dimensional log line per service boundary, consolidating high-cardinality context for efficient querying and incident analysis.
Instrument your app by creating a middleware that initializes a wide event at request start, enriches it throughout processing, and emits one canonical log line at the end.
High-intent search queries and answers about installing and using this skill.
A wide event is a single, highly-dimensional structured log line emitted per request at service boundaries. It consolidates routing, identity, and high-cardinality context into one canonical log line for efficient querying and incident analysis.
You consolidate request logs by creating middleware that initializes a wide event at request start, enriches it with context like user and feature flags during processing, and emits one canonical log line in a finally block at the end.
You need canonical log lines in distributed systems and microservices when traditional logging scatters context across statements, making it hard to correlate incidents and understand the complete request path across service boundaries.
The best way to handle log volume is using tail sampling to decide which wide events to retain. This approach preserves critical traces like errors, latency outliers, and VIP requests over naive random sampling.
Yes, wide event logging specifically supports high-cardinality context. You enrich the event throughout the request lifecycle by attaching user details, feature flags, cart data, errors, and business metrics before emitting the final log line.
agusmdevEmit one JSON wide-event log per request per service.
jamesaphoenixCorrelate traces, logs, and metrics to diagnose distributed failures.
ajianazOrchestrate end-to-end observability and monitoring for complex applications.
nbbaierDefine structured logging and correlation ID practices for distributed production services.
