Telemetry on ZAPP

Containers

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

ZAPP containers can embed multiple data formats in one container. Key features include:

Minimal overhead: 4-byte container header and 10-byte header for each payload
Variable-length multiple payloads with no inherent container size limit
Extensible via IANA ID + TypeID mechanism

Time-series telemetry

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

ZAPP represents decoded sensor telemetry as time-series models. Operators usually interact with this model indirectly through pipeline components, the ZAPP Aggregator, and gRPC subscriptions.

A time-series model contains:

readings, which group telemetry by sensor ID
Instance readings, which represent individual samples
Window readings, which represent aggregated samples over a time interval
snapshots, which represent the latest known values for multiple sensors at one timestamp

Pipeline components use time-series models when telemetry has been decoded and associated with the sensor manifest. For example, payloadProcessor converts NVIDIA time-series payloads into *timeseries.Model values, and redfishCollector emits *timeseries.Model values from Redfish polling.

Concepts

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

Use these pages to understand the telemetry concepts that ZAPP components and plugins share.

Pipeline components

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

A ZAPP pipeline is a YAML map of named components. Each component declares a type, component-specific fields, and optional targets. Targets connect one component output to another component input.

Components usually fit one of three roles:

Source components receive or collect telemetry
Processing components convert or route telemetry
Terminal components forward telemetry to a service, network endpoint, or consumer API

Channels

Pipeline components pass data through typed channels. Source and processing components expose outputs with targets, and downstream components receive those outputs as inputs. During startup, ZAPP creates the channels, connects each target to the named component, and validates that the receiving component accepts that input type.