nemo-relay-plugin-observability

Start with one exporter managed by the built-in Observability plugin, choosing the output that matches your inspection target: ATOF for raw events, ATIF for trajectories, or OpenTelemetry for OTLP tracing. Verify that single output before layering additional telemetry destinations.

Relay 0.6 uses observability configuration version 2 with separate OpenTelemetryConfig/OpenTelemetrySubscriber and OpenInferenceConfig/OpenInferenceSubscriber exporters. Relay 0.7 uses configuration version 3 with one typed OpenTelemetry exporter offering full, gen_ai, and openinference projections.

Create an AtifExporter with session and agent metadata, register it before instrumented work, run scoped tool and LLM activity, then call export() or export_json(). Use one exporter per run or call clear() between runs, and confirm schema_version is ATIF-v1.7 before evaluation use.

Yes. Use the OpenTelemetry exporter with http_binary transport and an OTLP endpoint for Jaeger, Tempo, or a collector; for Phoenix, use the OpenInference path (standalone exporter in 0.6, the openinference typed projection in 0.7). Multiple subscribers can observe the same event stream concurrently.

Common causes include the subscriber not being registered before scoped work, missing flush or shutdown calls, wrong transport for the binding, or events emitted outside active scopes. In 0.6, grpc also requires an active Tokio runtime; check construction logs and collector traffic first.

Use manual subscriber or exporter APIs only when a test, script, or application needs direct control over registration names, collection windows, or flush timing. The plugin-managed configuration remains the default for reusable process setup, and both paths consume the same canonical event stream.