wide-events

Define canonical log lines with identity, user, business, performance, and outcome fields.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/front-depiction/claude-setup --skill wide-events
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wide-events
Source: https://github.com/front-depiction/claude-setup/tree/main/skills/wide-events
Command: npx skills add https://github.com/front-depiction/claude-setup --skill wide-events

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Traditional logging often produces scattered, unstructured data across services, hindering rapid incident investigation. Wide events advocate a single, rich canonical log line per request, enabling fast queries and better correlation.

Core Features & Use Cases

  • Canonical log line design that attaches all relevant context to one event per request.
  • Field taxonomy and data modeling for identity, user, business, performance, and outcome.
  • Guidance for instrumentation and debugging across distributed systems.

Quick Start

Design a canonical log line for a sample request, including the identity, user, business, performance, and outcome fields, and show how it enables end-to-end querying.

Frequently Asked Questions about wide-events

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

FAQPage Schema
What are wide events in distributed systems observability?

Wide events are a single, rich canonical log line per request in distributed systems. They solve fragmented logging by attaching all relevant context—identity, user, business, performance, and outcome—to one event, enabling rapid incident investigation and better correlation.

How do I design a canonical log line for structured logging?

Design a canonical log line for structured logging by defining a schema with identity, user, business, performance, and outcome fields. This wide-events approach attaches all relevant contextual data to a single event per request, enabling fast end-to-end querying across services.

When do I need canonical logs for incident investigation?

You need canonical logs for incident investigation when traditional structured logging produces scattered, unstructured data across distributed services. Wide events consolidate contextual data into a single rich log line per request, enabling rapid queries and correlation during debugging.

How do I apply tail-sampling for span annotation in distributed systems?

Apply tail-sampling for span annotation in distributed systems by using a schema-driven instrumentation strategy. This approach captures contextual data across services, defining a canonical structure with identity and outcome fields to selectively sample and annotate traces for performance analysis.

What fields should I include in a canonical log structure for observability?

A canonical log structure for observability should include field taxonomy for identity, user, business, performance, and outcome. This schema-driven instrumentation ensures wide events capture all relevant contextual data, enabling fast queries and end-to-end correlation across distributed services.