opentelemetry

Configure OpenTelemetry SDKs for tracing, metrics, and logging in Node.js, Python, Go, and Rust.

6|1|Updated Feb 27, 2026
One-click install
npx skills add https://github.com/RepairYourTech/cfsa-antigravity --skill opentelemetry-repairyourtech
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: opentelemetry
Source: https://github.com/RepairYourTech/cfsa-antigravity/tree/main/.agent/skill-library/stack/observability/opentelemetry
Command: npx skills add https://github.com/RepairYourTech/cfsa-antigravity --skill opentelemetry-repairyourtech

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you implement comprehensive observability by setting up OpenTelemetry for distributed tracing, metrics, and structured logging, ensuring you can effectively monitor and debug complex, distributed applications.

Core Features & Use Cases

  • Distributed Tracing: Track requests as they flow across multiple services.
  • Metrics Collection: Gather application performance metrics like request counts and latency.
  • Structured Logging: Ensure logs are correlated with traces for easier debugging.
  • Instrumentation: Supports auto and manual instrumentation for various languages (Node.js, Python, Go, Rust).
  • Exporter Configuration: Set up exporters for backends like Jaeger, Zipkin, or OTLP.
  • Use Case: Integrate OpenTelemetry into your microservices architecture to visualize request paths, identify bottlenecks, and correlate errors across services.

Quick Start

Configure OpenTelemetry for your Node.js service using the provided SDK setup example.

Frequently Asked Questions about opentelemetry

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

FAQPage Schema
How do I set up distributed tracing for microservices across multiple languages?

Distributed tracing for microservices is configured by setting up the OpenTelemetry SDK in Node.js, Python, Go, or Rust, enabling context propagation and OTLP exporters to track requests across services.

How does OpenTelemetry correlate structured logs with traces for debugging?

OpenTelemetry correlates structured logging with distributed traces by injecting trace context into log entries, allowing you to filter and analyze logs alongside specific request paths across microservices.

Can I use this to configure metrics collection and OTLP exporters for my application?

Yes, you can configure metrics collection and OTLP exporters to send telemetry data to backends like Jaeger or Zipkin, capturing application performance metrics such as request counts and latency.

What's the best way to instrument a Node.js service for observability?

The best way to instrument a Node.js service for observability is using the OpenTelemetry SDK to configure auto or manual instrumentation, capturing traces, metrics, and structured logs for comprehensive monitoring.

When do I need context propagation in distributed tracing?

Context propagation in distributed tracing is needed when tracking requests as they flow across multiple microservices, ensuring the trace context is maintained across service boundaries for accurate bottleneck identification.