메뉴
Maintain or extend NeMo Relay observability surfaces across ATIF, OpenTelemetry, and OpenInference
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | maintain-observability |
| description | Maintain or extend NeMo Relay observability surfaces across ATIF, OpenTelemetry, and OpenInference |
| author | NVIDIA Corporation and Affiliates |
| license | Apache-2.0 |
Use karpathy-guidelines alongside this skill for implementation or review
work. Keep changes scoped, surface assumptions, and define focused validation
before editing.
Use this skill when changing event fields, exporter behavior, subscriber config, or binding parity for ATIF, OpenTelemetry, or OpenInference.
crates/core/src/observability/atif.rscrates/core/src/observability/otel.rscrates/core/src/observability/openinference.rsdocs/about/concepts/subscribers.md and
docs/export-observability-data/about.mdjust test-rust if event
fields changed.just test-python, just test-go, and just test-node when
binding-native config or lifecycle changed.docs/about/concepts/subscribers.mddocs/export-observability-data/about.mddocs/export-observability-data/code-examples.mdcrates/core/src/observability/atif.rscrates/core/src/observability/otel.rscrates/core/src/observability/openinference.rsvalidate-changeCompare 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 the NeMo Relay adaptive surface across config, plugins, docs, and bindings; use this when users still say optimizer
Maintain NeMo Relay package metadata, module paths, generated artifacts, and release-facing build surfaces