jido-otel

You map Jido observability hooks onto OpenTelemetry spans and tracing exporters to integrate tracing into Jido applications. This cleanly separates the core observability facade from OpenTelemetry specifics.

Span and correlation ID propagation maps Jido observability hooks onto OpenTelemetry spans to validate how trace identifiers cross package boundaries. This approach audits observability boundaries across packages.

Using the dedicated jido-otel module is the best way to configure a tracer backend and exporter for Jido workflows. It separates tracer integration from exporter configuration with runnable examples and best practices.

You can instrument Jido observability hooks without coupling core logic to tracing specifics. The jido-otel module maintains a clean separation between span lifecycles and core application logic.

No additional dependencies are required to implement tracing exporters with jido-otel. You read the builder notes and implement a basic OpenTelemetry tracer to begin emitting spans directly in your Jido app.