Run any Skill in Manus with one click

Get Started

nemo-relay-export-otel

Stars73

Forks40

UpdatedJuly 1, 2026 at 15:57

Configure and use NeMo Relay OpenTelemetry export for OTLP-compatible tracing backends

Installation

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.

Run Skill in Manus

Source

NVIDIA

NVIDIA/NeMo-Relay

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

2 files

SKILL.md

readonly

name	nemo-relay-export-otel
description	Configure and use NeMo Relay OpenTelemetry export for OTLP-compatible tracing backends
author	NVIDIA Corporation and Affiliates
license	Apache-2.0

Export OpenTelemetry Traces

Use this skill when the destination is an OTLP/OpenTelemetry backend such as an OpenTelemetry Collector, Jaeger, Tempo, or Honeycomb.

Default Path

Build the binding-specific OpenTelemetryConfig
Set endpoint, service name, and any required headers
Construct the subscriber
Register it before running scoped work
Deregister, flush, and shut down when the process or subsystem is done

Embedded OpenTelemetry Semantics

OpenTelemetry export maps NeMo Relay runtime events into OTLP traces for tracing backends and collectors.
Configure transport, endpoint, service_name, optional namespace and version, instrumentation scope, headers, resource attributes, and timeout.
Start with http_binary transport and an OTLP traces endpoint such as a local collector on port 4318 unless deployment requirements differ.
grpc transport is available when a Tokio runtime is active.
Use explicit config objects in application code; environment variables may be honored by the underlying exporter but should not be the only source of application behavior.
Register before the first instrumented request, use stable service identity, keep auth and endpoints out of source code, flush during graceful shutdown, and redact sensitive payloads before production export.
Validate export by checking subscriber construction, collector requests, backend spans for scopes/tools/LLMs, and span grouping by root scope.

Things To Confirm

Transport: http_binary vs grpc
Endpoint and auth headers
Service naming and resource attributes
Whether deterministic flush-before-exit is required
Whether the chosen binding and target support the desired transport

Troubleshooting Focus

No spans visible
Wrong endpoint or auth headers
Events emitted outside active scopes
grpc selected without a Tokio runtime
Forgetting register/deregister or flush/shutdown steps

Related Skills

nemo-relay-setup-observability
nemo-relay-export-openinference
nemo-relay-debug-runtime-integration

More from this repository

same repository

draft-release-notes

NVIDIA/NeMo-Relay

Compare 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.

2026-07-0873

contribute-docs

NVIDIA/NeMo-Relay

Contribute documentation or example changes that stay aligned with NeMo Relay public behavior

2026-07-0273

nemo-relay-build-plugin

NVIDIA/NeMo-Relay

Build and package reusable NeMo Relay runtime behavior as a config-activated plugin with validation and rollback-safe registration

2026-07-0273

add-binding-feature

NVIDIA/NeMo-Relay

Add or change a public NeMo Relay API surface across the core runtime and every affected binding

2026-07-0173

maintain-observability

NVIDIA/NeMo-Relay

Maintain or extend NeMo Relay observability surfaces across ATIF, OpenTelemetry, and OpenInference

2026-07-0173

maintain-optimizer

NVIDIA/NeMo-Relay

Maintain or extend the NeMo Relay adaptive surface across config, plugins, docs, and bindings; use this when users still say optimizer

2026-07-0173

Export OpenTelemetry Traces

Use this skill when the destination is an OTLP/OpenTelemetry backend such as an OpenTelemetry Collector, Jaeger, Tempo, or Honeycomb.

Default Path

Build the binding-specific OpenTelemetryConfig

Set endpoint, service name, and any required headers

Construct the subscriber

Deregister, flush, and shut down when the process or subsystem is done

Embedded OpenTelemetry Semantics

OpenTelemetry export maps NeMo Relay runtime events into OTLP traces for tracing backends and collectors.

Configure transport, endpoint, service_name, optional namespace and version, instrumentation scope, headers, resource attributes, and timeout.

Start with http_binary transport and an OTLP traces endpoint such as a local collector on port 4318 unless deployment requirements differ.

grpc transport is available when a Tokio runtime is active.

Use explicit config objects in application code; environment variables may be honored by the underlying exporter but should not be the only source of application behavior.

Register before the first instrumented request, use stable service identity, keep auth and endpoints out of source code, flush during graceful shutdown, and redact sensitive payloads before production export.

Validate export by checking subscriber construction, collector requests, backend spans for scopes/tools/LLMs, and span grouping by root scope.

Things To Confirm

Transport: http_binary vs grpc

Endpoint and auth headers

Service naming and resource attributes

Whether deterministic flush-before-exit is required

Whether the chosen binding and target support the desired transport

Troubleshooting Focus

No spans visible

Wrong endpoint or auth headers

Events emitted outside active scopes

grpc selected without a Tokio runtime

Forgetting register/deregister or flush/shutdown steps

Related Skills

nemo-relay-setup-observability

nemo-relay-export-openinference

nemo-relay-debug-runtime-integration