Skip to navigation

Observability

View as MarkdownOpen in Claude

BNR exposes standard Kubernetes workload status, NIM HTTP health endpoints, metrics, and runtime logs. Triton and application logs are available through the pod logs and, when enabled, the NIM logs PVC.

Kubernetes Status

Check Helm release status:

helm status bnr-h4m-sample

Check pods and deployments:

kubectl get pods -o wide
kubectl get deploy
kubectl describe pod <pod-name>

On Red Hat OpenShift, replace kubectl with oc.

Logs

View BNR NIM logs:

kubectl logs deploy/<nim-app-name> -c <nim-app-name>

If the chart uses a different container name, list containers first:

kubectl get pod <pod-name> -o jsonpath='{.spec.containers[*].name}'

NIM HTTP Endpoints

The BNR NIM container exposes HTTP endpoints on port 8000, and the service chart publishes them on the <appName>-endpoint service’s nim-http port.

EndpointPurpose
/v1/health/liveLiveness and startup probe endpoint.
/v1/health/readyReadiness probe endpoint.
/v1/metricsMetrics endpoint.
/intensity_ratioRuntime denoising intensity get/set endpoint.

Persistent Logs

The service chart and operator can enable persistent NIM logs:

nimLogs:
enabled: true
size: "5Gi"

NMOS

When nmos.enabled=true, verify that the sender, receiver, and BNR NIM are registered in the NMOS Connection Manager UI. The expected labels are as follows:

  • BNR Audio Sender
  • BNR-NIM
  • BNR Audio Receiver

SRT Preview

For the demo chart, verify receiver output:

ffplay "srt://<node-internal-ip>:32090"