Telemetry

Scope: This document covers DPS-side behavior only. For configuration, see the Deployment Guide.

Overview

Telemetry in DPS provides real-time power consumption data from datacenter entities via streaming sensors. This data enables excursion detection — identifying when power consumption exceeds configured limits — and automated mitigation to bring power back to compliance.

Note: A Telemetry Provider must be enabled for excursion detection and mitigation to be active. Without it, DPS continues to operate normally but does not receive real-time power data.

How Telemetry Data Flows from Zapp to DPS

1. Sensor mapping. Each device in the DPS topology is associated with a Zapp sensor ID. This links a physical power sensor to the corresponding device in the DPS hierarchy (node, PDU, rack, etc.).

2. Streaming connection. When the topology becomes active, DPS opens a streaming connection to Zapp and subscribes to all mapped sensors. Zapp sends power readings continuously, only transmitting values that have changed.

3. Power aggregation. DPS takes the raw per-device readings and aggregates them bottom-up through the topology tree. For example, individual node power readings are summed up to their parent rack, then to the PDU, and so on up the hierarchy. When a device has multiple parents, its power is split evenly across them.

4. Excursion check. After each aggregation, DPS compares every device’s aggregated power against its configured operational limit. If the aggregated power exceeds the limit, the device is flagged as being in a power excursion.

Further Reading

• Entities - Hardware resources that can be associated with telemetry sensors
• Excursion Mitigation - Automated response to power excursions
• Enabling Telemetry Provider - Configuring the telemetry provider