一键导入
nemo-relay-export-otel
Configure and use NeMo Relay OpenTelemetry export for OTLP-compatible tracing backends
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Configure and use NeMo Relay OpenTelemetry export for OTLP-compatible tracing backends
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
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.
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
| 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 |
Use this skill when the destination is an OTLP/OpenTelemetry backend such as an OpenTelemetry Collector, Jaeger, Tempo, or Honeycomb.
OpenTelemetryConfigtransport, endpoint, service_name, optional namespace and
version, instrumentation scope, headers, resource attributes, and timeout.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.http_binary vs grpcgrpc selected without a Tokio runtimenemo-relay-setup-observabilitynemo-relay-export-openinferencenemo-relay-debug-runtime-integration