<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Dsx on ZAPP</title><link>/datacenter/zapp/tags/dsx/</link><description>Recent content in Dsx on ZAPP</description><generator>Hugo</generator><language>en-US</language><atom:link href="/datacenter/zapp/tags/dsx/index.xml" rel="self" type="application/rss+xml"/><item><title>DSX plugin</title><link>/datacenter/zapp/docs/plugins/dsx-plugin/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/datacenter/zapp/docs/plugins/dsx-plugin/</guid><description>&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</description></item><item><title>DSX plugin example</title><link>/datacenter/zapp/docs/examples/dsx-plugin/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/datacenter/zapp/docs/examples/dsx-plugin/</guid><description>&lt;p&gt;Use this example to deploy a ZAPP Listener that uses DSX plugin components to collect GPU power metrics from Redfish-capable hosts.&lt;/p&gt;
&lt;p&gt;The standard ZAPP Listener binary includes the DSX component registrations. This example configures the registered &lt;code&gt;dsxMetrics&lt;/code&gt; component type in the listener pipeline.&lt;/p&gt;
&lt;h2 id="deployment-pattern"&gt;Deployment pattern&lt;/h2&gt;
&lt;p&gt;Deploy the &lt;a href="/datacenter/zapp/docs/deployment/zapp-aggregator/"&gt;ZAPP Aggregator&lt;/a&gt;
 first. Then deploy a ZAPP Listener with a DSX pipeline.&lt;/p&gt;
&lt;p&gt;In this pattern:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code&gt;zapp.listeners&lt;/code&gt; defines and enables the DSX Redfish listener&lt;/li&gt;
&lt;li&gt;&lt;code&gt;dsxMetrics&lt;/code&gt; manages the host inventory and polls Redfish metrics&lt;/li&gt;
&lt;li&gt;&lt;code&gt;DSX_REDFISH_PROXY_ENDPOINT&lt;/code&gt; configures an optional deployment-wide Redfish proxy endpoint&lt;/li&gt;
&lt;li&gt;&lt;code&gt;known_sensors_file&lt;/code&gt; loads the chart-provided DSX sensor catalog&lt;/li&gt;
&lt;li&gt;&lt;code&gt;host_persistence_path&lt;/code&gt; preserves host registrations in the listener data volume&lt;/li&gt;
&lt;li&gt;&lt;code&gt;metrics_service.listen_address&lt;/code&gt; exposes the DSX management gRPC service inside the listener pod&lt;/li&gt;
&lt;li&gt;&lt;code&gt;aggregatorStreamer&lt;/code&gt; forwards time-series telemetry to the ZAPP Aggregator&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="encryption-secret"&gt;Encryption Secret&lt;/h2&gt;
&lt;p&gt;The built-in DSX listener persists managed host registrations. Before you enable the listener, create a Kubernetes Secret for the persistence encryption key:&lt;/p&gt;</description></item></channel></rss>