OpenInference
Use the openinference section when you want NeMo Relay lifecycle events
exported as OTLP trace spans with OpenInference-oriented semantics.
OpenInference export maps model-centric payloads directly into trace
attributes. Scope, tool, and LLM start inputs become input.value; end outputs
become output.value; LLM usage metadata maps to token-count attributes when
the provider response includes usage information. For LLM spans, NeMo Relay
emits flattened request and response message attributes from typed codec
annotations and supported replay request/response payloads. Typed codec
annotations also provide tool schema, finish-reason, and invocation-parameter
attributes when those fields are available.
plugins.toml Example
This configuration registers a plugin-owned OpenInference subscriber and sends OpenInference-style OTLP spans to Phoenix or another compatible backend.
Fields
OpenInference uses the same OTLP section shape as OpenTelemetry:
Expected Output
The backend should show OpenInference-oriented spans for scopes, tools, and LLM calls grouped by root scope. LLM usage metadata appears as token counters when provider responses include usage information. LLM request and response messages, system prompts, and model-emitted tool calls are emitted as flattened OpenInference attributes when available from codec annotations or supported replay request/response payloads. Tool schemas, finish reasons, and invocation parameters are emitted when typed codec annotations supply them. Exported LLM attributes exclude request headers and other non-observable transport metadata.
Each lifecycle span includes nemo_relay.uuid and nemo_relay.parent_uuid
attributes. These values match ATIF step.extra.ancestry.function_id and
step.extra.ancestry.parent_id for the same events. For plugin-managed ATIF,
the root agent span’s nemo_relay.uuid also matches the ATIF session_id.
Backend-native trace_id and span_id values are not written into ATIF.
Redact sensitive event payloads with sanitize guardrails before production export.
Plugin Configuration
Use plugin configuration when the application should let NeMo Relay own the OpenInference subscriber lifecycle.
Python
Node.js
Rust
Manual API
Use the manual subscriber API when you need an explicit subscriber name or
direct force_flush control.
Python
Node.js
Rust
Common Validation Failures
transportis nothttp_binaryorgrpc.- Headers or resource attributes are not string-to-string maps.
- The OpenInference feature is unavailable in the current build or target.
- Tool and LLM calls do not use managed helpers, so spans contain only scope lifecycle data.