Observability
This page is for version 0.7.0.
For other versions, use one of these documentation indexes:
- Main (default): https://docs.nvidia.com/nemo/gym/main/llms.txt
- 0.7.0: https://docs.nvidia.com/nemo/gym/v0.7.0/llms.txt
- 0.6.0: https://docs.nvidia.com/nemo/gym/v0.6.0/llms.txt
- 0.5.1: https://docs.nvidia.com/nemo/gym/v0.5.1/llms.txt
- 0.5.0: https://docs.nvidia.com/nemo/gym/v0.5.0/llms.txt
- 0.4.0: https://docs.nvidia.com/nemo/gym/v0.4.0/llms.txt
- 0.3.0: https://docs.nvidia.com/nemo/gym/v0.3.0/llms.txt
- 0.2.1: https://docs.nvidia.com/nemo/gym/v0.2.1/llms.txt
NeMo Gym provides two independent observability features:
| Feature | Use it to | Enable with |
|---|---|---|
| Rollout evidence | Inspect model calls, agent activity, and saved trajectory health | observability_enabled and model_call_capture_dir |
| OpenTelemetry | Trace requests across services and monitor runtime metrics and logs | telemetry.enabled or NEMO_GYM_OTEL_ENABLED=1 |
Each feature has its own configuration. You can enable either or both.
Get Started
Rollout Evidence
Collect and inspect model-call capture, agent observations, and normalized trajectories.
Collector for Submitted Jobs
Run an OpenTelemetry Collector beside every gym eval submit job: engine, GPU and OTLP data with a per-run identity.
OpenTelemetry
Export distributed traces, metrics, and correlated logs through nemo-lens.