logging

Emit one structured log event per HTTP request with user context and performance metrics.

5.2k|543|Updated Jan 27, 2015
One-click install
npx skills add https://github.com/lukevella/rallly --skill logging-lukevella
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: logging
Source: https://github.com/lukevella/rallly/tree/main/.agents/skills/logging
Command: npx skills add https://github.com/lukevella/rallly --skill logging-lukevella

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Logs are often scattered and inconsistent; this guide defines a uniform, wide-event logging pattern to enable fast querying and robust observability.

Core Features & Use Cases

  • Single wide event per request containing all contextual information (request metadata, user context, business context, and performance metrics).
  • Structured, high-cardinality data to support efficient filtering, correlation, and tracing across services.
  • Use Cases: debugging failures, audit trails, performance monitoring, and proactive alerting.

Quick Start

Instrument your services to emit a single wide event per request after authentication.

Frequently Asked Questions about logging

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

FAQPage Schema
What is wide-event logging and how does it improve observability?

Wide-event logging emits a single structured log per request containing all contextual metadata, user data, and metrics, replacing scattered logs to enable fast querying and robust observability across services.

How do I implement uniform request logging across microservices?

Instrument services with middleware that collects request metadata, authenticated user context, and performance metrics, then emits one comprehensive structured event after request completion to centralize observability.

Can I use wide-event logging for background jobs and event pipelines?

Yes, wide-event logging applies to HTTP requests across microservices, background jobs, and event pipelines, capturing authenticated user context and business data to support audit trails and debugging.

Does wide-event logging support trace-id correlation across services?

Yes, wide-event logging produces structured, high-cardinality data with trace-id and request context to support efficient filtering, correlation, and tracing across distributed services.

What's the best way to structure logs for efficient querying and alerting?

Emit a single wide event per request containing structured, high-cardinality data including request metadata, user context, and performance metrics to support efficient filtering and proactive alerting.