Monitoring on ZAPP

Deploy the ZAPP Aggregator

Mon, 01 Jan 0001 00:00:00 +0000

Deploy the ZAPP Aggregator before deploying ZAPP Listener instances.

The ZAPP Aggregator receives telemetry from listeners and exposes listener gRPC, UDP telemetry ingest, subscriber gRPC, metrics, and manifest endpoints.

ZAPP Aggregator values

Most deployments only need to review the image, replica count, ports, resources, metrics, and ServiceMonitor settings.

zappAggregator:
 enabled: true
 image:
 repository: nvcr.io/nvidia/zapp-aggregator
 tag: ""
 pullPolicy: IfNotPresent

 replicas: 1
 logLevel: info
 metricsPort: 8888
 manifestUI: true

 containerPorts:
 listenerGrpc: 9991
 udpTelemetry: 9992
 clientGrpc: 9999

 serviceMonitor:
 enabled: false
 interval: 30s

Important fields:

NVIDIA ZAPP documentation

Mon, 01 Jan 0001 00:00:00 +0000

Important

NVIDIA ZAPP Aggregation Protocol Pipeline is currently offered as a Developer Preview. The software may have limitations, may change significantly, and includes functionality that continues to be refined through testing and feedback. It should not be used in production environments except as part of an authorized collaboration.

Use this documentation to deploy and operate ZAPP telemetry infrastructure on Kubernetes.

These pages cover ZAPP concepts, components, pipeline configuration, plugins, deployment, and example listener configurations.

Redfish listener architecture

Mon, 01 Jan 0001 00:00:00 +0000

The Redfish listener example combines Redfish sensor discovery, a ZAPP Listener pipeline, and ZAPP Aggregator forwarding.

The Redfish listener discovers or collects telemetry from Redfish-enabled baseboard management controllers (BMCs) and forwards telemetry to the ZAPP Aggregator.

Main components

BMC Redfish endpoints: BMC Redfish endpoints provide sensor metadata and telemetry from managed infrastructure.
Sensor pipeline: The envPlugins.sensorPipeline configuration runs before pipeline components start. It loads or discovers sensors and populates the listener sensor manifest.
Redfish listener pipeline: The listener pipeline runs inside the zapp container. For Redfish deployments, the pipeline includes Redfish configuration and forwards telemetry to an aggregatorStreamer component.
ZAPP Aggregator: The ZAPP Aggregator receives telemetry from the listener and exposes metrics, manifest data, and subscriber gRPC access.

Data flow

The listener reads the pipeline file and expands environment and secret references.
The sensor pipeline reads envPlugins.sensorPipeline.
ZAPP discovers or loads Redfish sensors into the manifest.
Pipeline components start.
The listener forwards telemetry to the ZAPP Aggregator.
Operators inspect /metrics, /manifest, or /manifest.json to validate deployment health.

The Helm chart mounts the pipeline at /config/pipeline.yaml, mounts Redfish credential files as Kubernetes Secrets, and passes the ZAPP Aggregator address to the listener with --aggregator.

Redfish listener example

Mon, 01 Jan 0001 00:00:00 +0000

Use this example to understand, configure, monitor, and troubleshoot ZAPP telemetry collection for Redfish-enabled infrastructure.

Start with Deploy ZAPP Listeners if you already know the topology and need Helm values.

ZAPP overview

Mon, 01 Jan 0001 00:00:00 +0000

ZAPP collects telemetry from infrastructure systems and forwards it through a configurable pipeline. Many deployments include one or more ZAPP Listeners and one ZAPP Aggregator.

ZAPP Listeners collect or receive telemetry near the source. A ZAPP Aggregator receives telemetry from multiple listeners and exposes one client-facing endpoint.

ZAPP Listener

A ZAPP Listener runs a configured telemetry pipeline. Depending on the pipeline, the listener can receive telemetry packets, discover sensors, collect Redfish telemetry, process payloads, and forward telemetry to the ZAPP Aggregator or directly to downstream consumers.

Configure the pipeline

Mon, 01 Jan 0001 00:00:00 +0000

The Redfish listener pipeline is embedded in the listener Helm values under zapp.listeners[].config.pipeline. The chart mounts the content at /config/pipeline.yaml.

The Redfish pipeline discovers sensors before components start, then forwards telemetry to the ZAPP Aggregator.

Sensor pipeline

Configure Redfish endpoints under envPlugins.sensorPipeline. This block runs before components start and populates the listener manifest.

envPlugins:
 sensorPipeline:
 maxRedfishConnections: 1
 redfishDevices:
 - endpoint: ${secrets.redfish_endpoint}
 username: ${secrets.redfish_username}
 password: ${secrets.redfish_password}
 version: 1.11.0
 manifest:
 path: /data/redfish-sensor-manifest.yaml
 forceReload: false

Important fields:

ZAPP Aggregator

Mon, 01 Jan 0001 00:00:00 +0000

The ZAPP Aggregator receives telemetry from ZAPP Listeners and exposes a stable API surface for consumers. Use it when you need centralized listener fan-in, manifest visibility, and one client endpoint for telemetry subscribers.

Helm values

Most deployments review image, replica, port, resource, and monitoring settings first.

zappAggregator:
 enabled: true
 image:
 repository: nvcr.io/nvidia/zapp-aggregator
 tag: ""
 pullPolicy: IfNotPresent

 replicas: 1
 metricsPort: 8888
 manifestUI: true

 containerPorts:
 listenerGrpc: 9991
 udpTelemetry: 9992
 clientGrpc: 9999

 serviceMonitor:
 enabled: false
 interval: 30s

Important fields:

Components

Mon, 01 Jan 0001 00:00:00 +0000

ZAPP deployments are built from two runtime components: ZAPP Listeners and the ZAPP Aggregator. Listener pipelines run near telemetry sources. The ZAPP Aggregator provides central fan-in, listener coordination, and consumer-facing APIs.

Use these pages to understand what each component runs, which configuration fields matter first, and where pipeline configuration fits into a deployment.

Monitor the Redfish listener

Mon, 01 Jan 0001 00:00:00 +0000

The listener and ZAPP Aggregator expose HTTP monitoring endpoints when metricsPort is greater than 0.

HTTP endpoints

Use these endpoints for health and telemetry inspection:

Endpoint	Purpose
`/metrics`	Prometheus metrics
`/manifest`	Sensor manifest web page
`/manifest.json`	Sensor manifest JSON

On the ZAPP Aggregator, the manifest page also shows connected listeners and sensor counts.

Port-forward the ZAPP Aggregator manifest

kubectl --namespace <namespace> port-forward svc/zapp-aggregator-metrics 8888:8888

Open the manifest page:

http://localhost:8888/manifest

Request manifest JSON:

Troubleshoot the Redfish listener

Mon, 01 Jan 0001 00:00:00 +0000

Start with Kubernetes readiness, then check listener configuration, ZAPP Aggregator connectivity, Redfish access, and telemetry validation.

Use Kubernetes checks, HTTP monitoring endpoints, and zest to isolate Redfish listener deployment problems.

Check pods and releases

helm list --namespace <namespace>
kubectl get pods --namespace <namespace>
kubectl get statefulsets --namespace <namespace>

If a pod is not ready, describe it and inspect recent events: