Plugins on ZAPP

DSX plugin

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

The DSX plugin adds pipeline components for collecting GPU and platform power metrics from Redfish-capable DSX hosts. Use it when a ZAPP Listener needs to manage a DSX host inventory, poll Redfish metric reports, and optionally emit selected Redfish metrics as ZAPP time-series telemetry.

The current ZAPP Listener binary registers the DSX component types. If you build a custom listener image, confirm that the image includes the DSX component registrations before you use these component types in a pipeline.

DSX plugin example

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

Use this example to deploy a ZAPP Listener that uses DSX plugin components to collect GPU power metrics from Redfish-capable hosts.

The standard ZAPP Listener binary includes the DSX component registrations. This example configures the registered dsxMetrics component type in the listener pipeline.

Deployment pattern

Deploy the ZAPP Aggregator first. Then deploy a ZAPP Listener with a DSX pipeline.

In this pattern:

zapp.listeners defines and enables the DSX Redfish listener
dsxMetrics manages the host inventory and polls Redfish metrics
DSX_REDFISH_PROXY_ENDPOINT configures an optional deployment-wide Redfish proxy endpoint
known_sensors_file loads the chart-provided DSX sensor catalog
host_persistence_path preserves host registrations in the listener data volume
metrics_service.listen_address exposes the DSX management gRPC service inside the listener pod
aggregatorStreamer forwards time-series telemetry to the ZAPP Aggregator

Encryption Secret

The built-in DSX listener persists managed host registrations. Before you enable the listener, create a Kubernetes Secret for the persistence encryption key:

Plugins

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

Plugins extend the ZAPP pipeline with additional component types. Use them when built-in components do not cover a site-specific telemetry source, protocol, processor, or output.

Plugin component packages live in the ZAPP repository and are compiled into the ZAPP Listener binary. When the listener starts, those packages register their component types with the pipeline registry.

Enable a plugin component by using its registered type in the listener pipeline:

components:
 dsx:
 type: dsxMetrics
 # DSX-specific configuration omitted.
 targets:
 - target: aggregator

 aggregator:
 type: aggregatorStreamer

For Kubernetes deployments, use a ZAPP Listener image that includes the plugin component registrations you need.