jido-otel

Instrument Jido with OpenTelemetry tracing and configure exporters.

7|Updated Mar 8, 2026
One-click install
npx skills add https://github.com/arrowcircle/jido-skills --skill jido-otel
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jido-otel
Source: https://github.com/arrowcircle/jido-skills/tree/main/skills/jido-otel
Command: npx skills add https://github.com/arrowcircle/jido-skills --skill jido-otel

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

OpenTelemetry integration guidance for Jido enables structured tracing, correlation across modules, and observable behavior without coupling core logic to tracing.

Core Features & Use Cases

  • Map Jido observability hooks to OpenTelemetry spans and events.
  • Separate tracer implementation from exporter configuration for flexibility.
  • Provide runnable examples and integration tips across jido and jido-otel.

Quick Start

Configure a basic tracer for a sample Jido action and export traces to a test OTLP endpoint.

Frequently Asked Questions about jido-otel

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

FAQPage Schema
How do I add OpenTelemetry tracing to Jido actions?

OpenTelemetry integration for Jido maps observability hooks to spans and events, enforcing separation of tracer logic from exporter configuration so core logic stays decoupled from tracing.

How do I configure an OTLP exporter for Jido tracing?

Configuring an OTLP exporter for Jido tracing involves separating the tracer implementation from the exporter configuration. This design provides flexibility, allowing you to export traces to a test OTLP endpoint while keeping the tracer logic independent.

How do correlation IDs work with OpenTelemetry instrumentation in Jido?

Correlation IDs in Jido OpenTelemetry instrumentation enable structured tracing and correlation across modules. By mapping observability hooks to spans, you achieve observable behavior across packages without coupling core logic to the tracing system.

Do I need to couple my core Jido logic to the tracer implementation?

You do not need to couple core Jido logic to the tracer implementation. The instrumentation enforces separation of tracer logic from exporter configuration, using the Jido.Observe model as the integration surface to maintain clean boundaries.

Are there runnable examples for setting up Jido observability with OpenTelemetry?

Runnable examples are provided for setting up Jido observability with OpenTelemetry. You can configure a basic tracer for a sample Jido action and export traces to a test OTLP endpoint using the provided integration tips and examples.

What is the best way to structure OpenTelemetry integration across Jido packages?

The best way to structure OpenTelemetry integration across Jido packages is to use the Jido.Observe model as the integration surface. This approach enforces separation of tracer logic from exporter configuration and provides structured observability across components like jido and jido-otel.