Generate structured, context-rich log events with correlation IDs for debugging.
npx skills add https://github.com/undg/.dot --skill logging-sucks-undg
Please help me install this Agent Skill. Skill: logging-sucks Source: https://github.com/undg/.dot/tree/main/opencode/.config/opencode/skill/logging-sucks Command: npx skills add https://github.com/undg/.dot --skill logging-sucks-undg
Logs are often unstructured and hard to query, making debugging and incident response slow. This skill promotes structured, context-rich logging with wide events per request, correlation IDs, and high-cardinality fields to enable fast root-cause analysis.
Configure your services to emit a single, wide, structured event per request with correlation IDs and high-cardinality fields.
High-intent search queries and answers about installing and using this skill.
Structured logging improves debugging by emitting context-rich, wide events per request with enforced fields like timestamp, level, and trace_id. This format enables fast querying and root-cause analysis during incident response.
To propagate trace IDs for cross-service tracing, configure services to emit structured events containing request_id and trace_id fields. This ensures correlation IDs traverse service boundaries for end-to-end visibility.
The best way to format logs for incident response is using canonical log lines. Emit one comprehensive, wide event per request containing 30-50 high-cardinality fields for effective, fast root-cause analysis.
Structured logging works effectively for distributed systems and microservices by enforcing context propagation. Correlation IDs traverse service boundaries, providing per-request visibility and supporting end-to-end observability.
Structured log events for observability must include timestamp, level, event, request_id, trace_id, service, and environment fields. They should also incorporate high-cardinality data while ensuring non-sensitive data handling.
Unstructured logs are hard to query because they lack context-rich, wide events and correlation IDs. Without enforced fields like trace_id and request_id, cross-service tracing and root-cause analysis become slow.
srstompGuide logging, metrics, and tracing across services with OpenTelemetry instrumentation.
elophantoAutomate incident response workflows from detection to post-mortem with severity-based teams.
dralgorhythmImplement centralized logging, metrics, and distributed tracing with OpenTelemetry.
elithrarDesign and enforce structured, context-rich logs for distributed applications.
