wide-events

Explain wide events and implementation strategies using OpenTelemetry spans and annotations.

68|13|Updated Aug 9, 2025
One-click install
npx skills add https://github.com/kriegcloud/beep-effect --skill wide-events-kriegcloud
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wide-events
Source: https://github.com/kriegcloud/beep-effect/tree/main/.claude/skills/wide-events
Command: npx skills add https://github.com/kriegcloud/beep-effect --skill wide-events-kriegcloud

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the limitations of traditional logging in distributed systems by promoting the concept of "wide events" or "canonical log lines" for improved observability and debugging.

Core Features & Use Cases

  • Conceptual Guide: Provides a framework for understanding and implementing wide events.
  • Instrumentation Strategy: Helps in deciding what context to capture and annotate within telemetry spans.
  • Debugging: Aids in correlating events and answering complex queries during incidents.
  • Use Case: When designing a new microservice, use this Skill's principles to ensure all relevant business, user, and technical context is captured in each telemetry event, making future debugging significantly easier.

Quick Start

Use the wide-events skill to understand the principles of capturing comprehensive context in telemetry.

Frequently Asked Questions about wide-events

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What are wide events and how do they improve observability in distributed systems?

Wide events are single, high-dimensionality log lines that capture comprehensive business, user, and technical context. They improve observability by replacing scattered, low-dimensionality logs with highly queryable events for easier debugging in distributed systems.

How do I implement canonical log lines using OpenTelemetry spans and annotations?

Implement wide events by annotating OpenTelemetry spans with essential context fields. This instrumentation strategy shifts telemetry from scattered logs to single, high-dimensionality events, capturing all relevant business and technical data for improved queryability.

When do I need wide events for debugging microservices?

You need wide events when debugging distributed systems and struggling with scattered logs. They correlate events into single high-dimensionality records, enabling you to answer complex queries during incidents by providing comprehensive business and technical context.

What context fields should I capture in telemetry events for better queryability?

Capture essential business, user, and technical context fields within OpenTelemetry span annotations. This ensures each wide event contains the necessary high-dimensionality data to answer complex queries during debugging and incidents in distributed systems.

What are common anti-patterns when shifting to wide events for logging?

Common wide events anti-patterns include failing to capture essential context fields and improperly configuring telemetry sampling. Avoiding these ensures your high-dimensionality events remain effective for answering complex debugging queries in distributed systems.

Does OpenTelemetry sampling work with high-dimensionality wide events?

Yes, wide events implementation details cover sampling strategies for OpenTelemetry. Proper sampling ensures that high-dimensionality telemetry events retain their queryability and debugging value without overwhelming system resources in distributed environments.