<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>NVIDIA ZAPP documentation on ZAPP</title><link>/datacenter/zapp/docs/</link><description>Recent content in NVIDIA ZAPP documentation on ZAPP</description><generator>Hugo</generator><language>en-US</language><atom:link href="/datacenter/zapp/docs/index.xml" rel="self" type="application/rss+xml"/><item><title>ZAPP overview</title><link>/datacenter/zapp/docs/overview/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/datacenter/zapp/docs/overview/</guid><description>&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;&lt;img src="/datacenter/zapp/images/docs/zapp-overview.svg" alt="ZAPP telemetry topology showing infrastructure sources feeding multiple listener pipelines, a central aggregator, and client and operator endpoints."&gt;
&lt;/p&gt;
&lt;p&gt;ZAPP Listeners collect or receive telemetry near the source. A ZAPP Aggregator receives telemetry from multiple listeners and exposes one client-facing endpoint.&lt;/p&gt;
&lt;h2 id="zapp-listener"&gt;ZAPP Listener&lt;/h2&gt;
&lt;p&gt;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.&lt;/p&gt;</description></item></channel></rss>