observability-logging-baseline

Configures OpenTelemetry-based logging, metrics, and tracing for services.

1|1|Updated Jan 3, 2026
One-click install
npx skills add https://github.com/mcj-coder/development-skills --skill observability-logging-baseline
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: observability-logging-baseline
Source: https://github.com/mcj-coder/development-skills/tree/main/skills/observability-logging-baseline
Command: npx skills add https://github.com/mcj-coder/development-skills --skill observability-logging-baseline

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the challenge of building and maintaining robust observability in software services, ensuring that logs, metrics, and traces are standardized, actionable, and efficient.

Core Features & Use Cases

  • Structured Logging: Implements message templates and correlation IDs for searchable, context-rich logs.
  • Metrics: Defines RED (Rate, Errors, Duration) and USE (Utilization, Saturation, Errors) metrics using OpenTelemetry standards.
  • Distributed Tracing: Enables end-to-end request tracking across services using W3C Trace Context.
  • Use Case: When developing a new microservice, use this Skill to ensure it's built with production-ready observability from day one, making debugging and performance monitoring straightforward.

Quick Start

Configure structured logging with message templates and correlation ID middleware for your service.

Frequently Asked Questions about observability-logging-baseline

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

FAQPage Schema
How do I set up structured logging with correlation IDs for a new microservice?

Structured logging for a new microservice requires implementing message templates and correlation ID middleware to generate searchable, context-rich logs. This ensures logs are standardized and actionable from day one.

What is the difference between RED and USE metrics in observability?

RED metrics measure service Rate, Errors, and Duration, while USE metrics track resource Utilization, Saturation, and Errors. Both are defined using OpenTelemetry standards to establish comprehensive performance monitoring.

How does distributed tracing work across service boundaries using W3C Trace Context?

Distributed tracing using W3C Trace Context enables end-to-end request tracking by propagating correlation IDs across service boundaries. This allows you to follow a single request's path through multiple microservices.

Can I use OpenTelemetry standards to add observability to an existing service?

Yes, OpenTelemetry standards can be applied to existing services to establish production-ready observability. You can integrate structured logging, metrics, and distributed tracing without needing a completely new architecture.

What's the best way to establish production-ready observability foundations?

The best way to establish observability foundations is using OpenTelemetry standards to implement structured logging, RED/USE metrics, and distributed tracing with W3C Trace Context, ensuring all telemetry data is correlated and actionable.