skills.rest
wildbitca
wildbitcaOFFICIAL
Explore all skills by this author →
WebsiteGitHub

common-observability

Standardize logs, traces, and metrics across polyglot microservices with OpenTelemetry.

1|Updated Mar 19, 2026
Search Tags:#logging#metrics#observability#tracing#opentelemetry#slo#correlation
One-click install
npx skills add https://github.com/wildbitca/ai-resources --skill common-observability
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: common-observability
Source: https://github.com/wildbitca/ai-resources/tree/main/skills/common-observability
Command: npx skills add https://github.com/wildbitca/ai-resources --skill common-observability

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Centralizes and codifies observability practices to improve reliability, debuggability, and performance visibility across services.

Core Features & Use Cases

  • Structured logging with JSON payloads and consistent field names.
  • OpenTelemetry-based distributed tracing with standardized span naming and context propagation.
  • Unified metrics collection with SLO-aware dashboards and alerting guidance.
  • Cross-service correlation using trace IDs to diagnose distributed workflows.

Quick Start

Instrument your services to emit JSON logs, propagate OpenTelemetry trace context, and expose standard metrics endpoints.

Frequently Asked Questions about common-observability

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

FAQPage Schema
How do I standardize observability across polyglot microservices?▼

To standardize observability across polyglot microservices, enforce consistent instrumentation, naming, and propagation of logs, traces, and metrics using OpenTelemetry, JSON-structured logs, and SLO-aligned metrics collection.

What is the best way to correlate logs and traces in distributed workflows?▼

The best way to correlate logs and traces in distributed workflows is by propagating OpenTelemetry trace IDs across services to diagnose distributed workflows and link JSON-structured log payloads.

How does OpenTelemetry help enforce consistent tracing and metrics collection?▼

OpenTelemetry enforces consistent tracing and metrics collection by standardizing span naming and context propagation while exposing standard metrics endpoints for SLO-aware dashboards and alerting.

Do I need JSON-structured logs for SLO-aligned metrics and tracing?▼

Yes, you need JSON-structured logs to satisfy the required technical standards for SLO-aligned metrics and OpenTelemetry tracing, ensuring consistent field names for reliable cross-service correlation.

Can I use this observability standardization for a single monolithic application?▼

This observability standardization is designed for polyglot microservice architectures to ensure consistent instrumentation and context propagation, making it excessive for a single monolithic application.

Related Skills

Explore More Software Engineering Skills→
ryan-nguyen-01ryan-nguyen-01
4

skill-observability-tracing

Set up O2S and S0S mobile phone service for seamless connectivity.

Community
Advanced
bipinksbipinks
3

monitoring-patterns

Configure Prometheus scrape configs, Grafana dashboards, and SLO/SLI alerting patterns.

Community
Advanced
dseirz-rgbdseirz-rgb

multi-service-debug

Correlate logs and traces to diagnose cross-service failures between Vercel and Cloud Run.

Community
Advanced
patricio0312revpatricio0312rev
5

observability-setup

Implement OpenTelemetry tracing, Prometheus metrics, and structured logging in Node.js applications.

Community
Advanced