Observability
NIM provides Prometheus metrics for Relight requests, the GPU, the server process, and the Python runtime. For per-model inference counts and latencies, use the Triton metrics. You can use these metrics to create dashboards with Grafana. By default, these metrics are available at http://0.0.0.0:8000/v1/metrics.
These commands need a NIM launched as in Getting Started, with ports 8000 and 9002 published, and curl.
You can use the following command to retrieve the metrics:
The following table describes the available metrics.
Both request metrics carry endpoint="/nvidia.ai4m.relighting.v1.VideoRelightingService/Relight" and count every request, including requests the NIM rejects before inference, such as RESOURCE_EXHAUSTED or INVALID_ARGUMENT. The process_* and python_* metrics describe the NIM’s HTTP front-end process, not the gRPC inference service or Triton. The Triton failure counters below count only inference that fails inside Triton.
HTTP Endpoints
Besides /v1/metrics, the HTTP port serves the following endpoints:
Triton Metrics
NIM also exposes Triton Inference Server metrics that provide detailed information about model inference performance, request handling, and system utilization. By default, these Triton metrics are available at http://localhost:9002/metrics.
Use the following command to retrieve the Triton metrics:
The following are key Triton metrics:
- Request metrics: Counts of successful and failed inference requests.
- Inference metrics: Request queue times, compute times, and overall request durations.
- Model metrics: Model loading times, execution counts, and batch statistics.
- Memory metrics: GPU and CPU memory usage for inference operations.
For comprehensive documentation on all available Triton metrics, their descriptions, and usage examples, see Metrics in the Triton Inference Server guide.