otel-observability

Enable OpenTelemetry traces, metrics, and logs across AgentStack components.

2|Updated Dec 14, 2025

Search Tags:#logs #metrics #observability #tracing #Prometheus #Grafana #OpenTelemetry

Ready to run

npx skills add https://github.com/raphaelmansuy/k8s-agent-stack --skill otel-observability

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: otel-observability
Source: https://github.com/raphaelmansuy/k8s-agent-stack/tree/main/archive/skills/otel-observability
Command: npx skills add https://github.com/raphaelmansuy/k8s-agent-stack --skill otel-observability

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill enables end-to-end observability across the AgentStack by implementing OpenTelemetry instrumentation for traces, metrics, and logs, enabling proactive monitoring and faster issue diagnosis.

Core Features & Use Cases

Distributed tracing: Instrument services to produce traces that illuminate cross-service call paths.
Metrics & dashboards: Export Prometheus-compatible metrics and integrate with Grafana for dashboards.
Structured logging: Ensure logs carry context for easier correlation with traces and metrics.
Agent health & monitoring: Gather telemetry data to monitor agent health and performance in production.

Quick Start

Configure your services to use the OTEL SDK and point collectors to the OTEL Collector endpoint. Start the observability stack and verify traces, metrics, and logs appear in Grafana dashboards.

Frequently Asked Questions about otel-observability

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

FAQPage Schema

How do I set up distributed tracing across microservices?▼

Distributed tracing illuminates cross-service call paths by instrumenting services with OpenTelemetry to produce traces. Configure your services to use the OTEL SDK, point collectors to the OTEL Collector endpoint, and export traces over gRPC to visualize request flows across API Gateway, Agents, Workers, and Control Plane components.

Can I export metrics to Prometheus and Grafana?▼

Yes. OpenTelemetry exports Prometheus-compatible metrics that integrate directly with Grafana for dashboards. Configure metric export endpoints, start the observability stack, and metrics will appear in Grafana alongside traces and logs for unified monitoring.

What's the best way to correlate logs with traces in production?▼

Structured logging with OpenTelemetry carries trace context through your logs, enabling correlation with distributed traces and metrics. This context propagation lets you follow a single request across services, making issue diagnosis faster when logs, traces, and metrics appear together in dashboards.

How do I monitor agent health and performance in AgentStack?▼

Instrument your AgentStack components with OpenTelemetry to gather telemetry data—traces, metrics, and logs—across API Gateway, Agents, Workers, and Control Plane. Batch processing with timeout and size controls, sampling, and graceful shutdown ensure efficient collection and export to monitoring dashboards.

Does OpenTelemetry support context propagation across service boundaries?▼

Yes. OpenTelemetry includes context propagation to maintain trace correlation as requests cross service boundaries. This ensures traces remain linked across API Gateway, Agents, Workers, and Control Plane, enabling end-to-end visibility of distributed request flows.

What observability gaps does OpenTelemetry instrumentation resolve?▼

OpenTelemetry closes observability gaps by enabling comprehensive traces, Prometheus metrics, and structured logs across AgentStack components. It provides resource-based service metadata, OTLP trace export over gRPC, batch processing controls, and sampling to support proactive monitoring and faster diagnosis.