logging-observability

Configure OpenTelemetry, structured logging, tracing, and metrics for production services.

Updated Mar 27, 2026
One-click install
npx skills add https://github.com/CenredJun/openclaw-claudecode-setup-kit --skill logging-observability-cenredjun
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: logging-observability
Source: https://github.com/CenredJun/openclaw-claudecode-setup-kit/tree/main/skills/logging-observability
Command: npx skills add https://github.com/CenredJun/openclaw-claudecode-setup-kit --skill logging-observability-cenredjun

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Production applications often lack consistent structured logs, distributed traces, and actionable metrics, making incidents slow and expensive to diagnose. This Skill provides patterns to avoid PII leaks, reduce alert noise, and ensure traceable requests across services so teams can detect and resolve outages faster.

Core Features & Use Cases

  • Structured logging: JSON log formats with redaction rules and log level strategy for production readiness.
  • Distributed tracing: Correlation IDs and OpenTelemetry SDK initialization to propagate W3C tracecontext across services.
  • Metrics & alerting: Prometheus metrics, SLI/SLO templates, Grafana dashboard design, and PagerDuty routing to prevent alert fatigue.
  • Use Case: Instrument a payment or order-processing service to emit structured logs, capture traces for each request, measure p99 latency and error budget, and page on-call when burn-rate thresholds are exceeded.

Quick Start

Initialize the OpenTelemetry SDK before any other imports and enable JSON structured logging with redaction rules and correlation ID propagation.

Frequently Asked Questions about logging-observability

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

FAQPage Schema
How do I implement structured logging with redaction rules for production applications?

Implement structured logging by emitting JSON formats with redaction rules and log level strategies. This prevents PII leaks and ensures production readiness across backend services like Node, Python, Go, and Java.

How does OpenTelemetry distributed tracing propagate W3C tracecontext across services?

OpenTelemetry propagates W3C tracecontext by initializing the SDK before other imports and using correlation IDs. This makes requests traceable across backend services to diagnose outages faster.

What is the best way to design Grafana dashboards and PagerDuty alert routing for SLI/SLO metrics?

Use Prometheus metrics and SLI/SLO templates to design Grafana dashboards and PagerDuty routing, preventing alert fatigue. This pages on-call teams only when error budget burn-rate thresholds are exceeded.

Does this observability approach work with both Python and Go backend services?

Yes, this observability approach applies to Node, Python, Go, and Java backend services. It initializes OpenTelemetry, structured JSON logging, and tracing uniformly across these languages.

How do I set up OpenTelemetry initialization to capture traces for each request?

Initialize the OpenTelemetry SDK before any other imports to capture traces for each request. This enables correlation ID propagation and W3C tracecontext across services for incident detection.