/datacenter/zapp/docs/concepts/Recent content in Concepts on ZAPPHugoen-US/datacenter/zapp/docs/concepts/containers/Mon, 01 Jan 0001 00:00:00 +0000/datacenter/zapp/docs/concepts/containers/<p>ZAPP containers can embed multiple data formats in one container. Key features include:</p> <ul> <li>Minimal overhead: 4-byte container header and 10-byte header for each payload</li> <li>Variable-length multiple payloads with no inherent container size limit</li> <li>Extensible via IANA ID + TypeID mechanism</li> </ul> <p><img src="../container.png" alt="Diagram of a ZAPP container header followed by multiple payloads and their headers"> </p>/datacenter/zapp/docs/concepts/time-series/Mon, 01 Jan 0001 00:00:00 +0000/datacenter/zapp/docs/concepts/time-series/<p>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.</p> <p>A time-series model contains:</p> <ul> <li><code>readings</code>, which group telemetry by sensor ID</li> <li>Instance readings, which represent individual samples</li> <li>Window readings, which represent aggregated samples over a time interval</li> <li><code>snapshots</code>, which represent the latest known values for multiple sensors at one timestamp</li> </ul> <p>Pipeline components use time-series models when telemetry has been decoded and associated with the sensor manifest. For example, <code>payloadProcessor</code> converts NVIDIA time-series payloads into <code>*timeseries.Model</code> values, and <code>redfishCollector</code> emits <code>*timeseries.Model</code> values from Redfish polling.</p>