<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Distributed on ZAPP</title><link>/datacenter/zapp/tags/distributed/</link><description>Recent content in Distributed on ZAPP</description><generator>Hugo</generator><language>en-US</language><atom:link href="/datacenter/zapp/tags/distributed/index.xml" rel="self" type="application/rss+xml"/><item><title>Redfish listener architecture</title><link>/datacenter/zapp/docs/examples/redfish-listener/architecture/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/datacenter/zapp/docs/examples/redfish-listener/architecture/</guid><description>&lt;p&gt;The Redfish listener example combines Redfish sensor discovery, a ZAPP Listener pipeline, and ZAPP Aggregator forwarding.&lt;/p&gt;
&lt;p&gt;&lt;img src="/datacenter/zapp/images/docs/redfish-listener-architecture.png" alt="Redfish listener architecture showing baseboard management controller Redfish endpoints, sensor discovery, the listener pipeline, and the ZAPP Aggregator."&gt;
&lt;/p&gt;
&lt;p&gt;The Redfish listener discovers or collects telemetry from Redfish-enabled baseboard management controllers (BMCs) and forwards telemetry to the ZAPP Aggregator.&lt;/p&gt;
&lt;h2 id="main-components"&gt;Main components&lt;/h2&gt;
&lt;dl&gt;
&lt;dt&gt;&lt;strong&gt;BMC Redfish endpoints&lt;/strong&gt;&lt;/dt&gt;
&lt;dd&gt;BMC Redfish endpoints provide sensor metadata and telemetry from managed infrastructure.&lt;/dd&gt;
&lt;dt&gt;&lt;strong&gt;Sensor pipeline&lt;/strong&gt;&lt;/dt&gt;
&lt;dd&gt;The &lt;code&gt;envPlugins.sensorPipeline&lt;/code&gt; configuration runs before pipeline components start. It loads or discovers sensors and populates the listener sensor manifest.&lt;/dd&gt;
&lt;dt&gt;&lt;strong&gt;Redfish listener pipeline&lt;/strong&gt;&lt;/dt&gt;
&lt;dd&gt;The listener pipeline runs inside the &lt;code&gt;zapp&lt;/code&gt; container. For Redfish deployments, the pipeline includes Redfish configuration and forwards telemetry to an &lt;code&gt;aggregatorStreamer&lt;/code&gt; component.&lt;/dd&gt;
&lt;dt&gt;&lt;strong&gt;ZAPP Aggregator&lt;/strong&gt;&lt;/dt&gt;
&lt;dd&gt;The ZAPP Aggregator receives telemetry from the listener and exposes metrics, manifest data, and subscriber gRPC access.&lt;/dd&gt;
&lt;/dl&gt;
&lt;h2 id="data-flow"&gt;Data flow&lt;/h2&gt;
&lt;ol&gt;
&lt;li&gt;The listener reads the pipeline file and expands environment and secret references.&lt;/li&gt;
&lt;li&gt;The sensor pipeline reads &lt;code&gt;envPlugins.sensorPipeline&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;ZAPP discovers or loads Redfish sensors into the manifest.&lt;/li&gt;
&lt;li&gt;Pipeline components start.&lt;/li&gt;
&lt;li&gt;The listener forwards telemetry to the ZAPP Aggregator.&lt;/li&gt;
&lt;li&gt;Operators inspect &lt;code&gt;/metrics&lt;/code&gt;, &lt;code&gt;/manifest&lt;/code&gt;, or &lt;code&gt;/manifest.json&lt;/code&gt; to validate deployment health.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;The Helm chart mounts the pipeline at &lt;code&gt;/config/pipeline.yaml&lt;/code&gt;, mounts Redfish credential files as Kubernetes Secrets, and passes the ZAPP Aggregator address to the listener with &lt;code&gt;--aggregator&lt;/code&gt;.&lt;/p&gt;</description></item><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>