Menu
Configure and use NeMo Relay OpenInference export for OTLP backends that understand OpenInference semantics
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | nemo-relay-export-openinference |
| description | Configure and use NeMo Relay OpenInference export for OTLP backends that understand OpenInference semantics |
| author | NVIDIA Corporation and Affiliates |
| license | Apache-2.0 |
Use this skill when the destination expects OpenInference semantic conventions, for example Arize Phoenix or another OpenInference-aware OTLP backend.
OpenInferenceConfigtransport, endpoint, service_name, optional namespace and
version, instrumentation scope, headers, resource attributes, and timeout.http_binary transport and an OTLP/HTTP traces endpoint. Use
grpc only when a Tokio runtime is active.input.value.output.value.root_uuid in the tracing backend.input.value from request content, not request headersnemo-relay-setup-observabilitynemo-relay-export-otelnemo-relay-typed-wrappers-codecsCompare NeMo Relay release branches and draft or update the documentation-site release notes. Use when preparing a release-notes update under docs/about-nemo-relay/release-notes, reviewing release-to-release changes, or gathering evidence for a current release summary.
Contribute documentation or example changes that stay aligned with NeMo Relay public behavior
Build and package reusable NeMo Relay runtime behavior as a config-activated plugin with validation and rollback-safe registration
Add or change a public NeMo Relay API surface across the core runtime and every affected binding
Maintain or extend NeMo Relay observability surfaces across ATIF, OpenTelemetry, and OpenInference
Maintain or extend the NeMo Relay adaptive surface across config, plugins, docs, and bindings; use this when users still say optimizer