opentelemetry

Instrument services to export traces, metrics, and logs to an OpenTelemetry collector.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/tylern91/dotfiles --skill opentelemetry-tylern91
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: opentelemetry
Source: https://github.com/tylern91/dotfiles/tree/main/agents/.agents/skills/opentelemetry
Command: npx skills add https://github.com/tylern91/dotfiles --skill opentelemetry-tylern91

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Instrument applications and infrastructure with OpenTelemetry for unified traces, metrics, and logs, enabling vendor-neutral observability and easier troubleshooting.

Core Features & Use Cases

  • Instrument microservices and monoliths with traces, metrics, and logs.
  • Auto-instrument common libraries and export telemetry to OTLP backends.
  • Use cases include latency debugging, SLO dashboards, and cross-service trace correlation.

Quick Start

Configure your services to export traces, metrics, and logs to an OpenTelemetry collector.

Frequently Asked Questions about opentelemetry

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

FAQPage Schema
How do I instrument microservices to export traces, metrics, and logs?▼

To instrument microservices, configure your services to export traces, metrics, and logs to a centralized OpenTelemetry collector using OTLP endpoints. This enables unified observability and cross-service trace correlation for troubleshooting.

What is OpenTelemetry auto-instrumentation for Python and Node.js?▼

OpenTelemetry auto-instrumentation automatically instruments common libraries in Python and Node.js applications to export telemetry data. It simplifies latency debugging and SLO dashboard creation by exporting traces, metrics, and logs to OTLP backends.

Can I use OpenTelemetry to instrument legacy applications for unified observability?▼

Yes, you can instrument legacy applications with OpenTelemetry to achieve unified observability. This vendor-neutral approach enables consistent traces, metrics, and logs export to centralized collectors like Jaeger, Tempo, or Prometheus-compatible backends.

Do I need an OTLP endpoint to collect OpenTelemetry traces and metrics?▼

Yes, an OTLP endpoint is required to export traces, metrics, and logs from your services to a centralized OpenTelemetry collector. Backends such as Jaeger, Tempo, or Prometheus-compatible collectors receive this telemetry data for analysis.

Does OpenTelemetry support Kubernetes deployments for observability instrumentation?▼

Yes, OpenTelemetry supports optional Kubernetes deployments for instrumenting cloud-native architectures. This allows microservices running in Kubernetes to export telemetry data to centralized collectors for unified observability and latency debugging.

What's the best way to achieve vendor-neutral observability for cloud-native architectures?▼

The best way to achieve vendor-neutral observability is instrumenting applications with OpenTelemetry. By exporting unified traces, metrics, and logs to a centralized collector, you enable easier troubleshooting and avoid vendor lock-in across microservices.