--- title: "MQTT for Data Center Power & Cooling Monitoring | ConnectMQ" description: "Stream PDU, CRAC, UPS and rack sensor data over a managed MQTT broker to your DCIM, NOC alerting and PUE reporting — published on change, TLS and per-site ACLs." url: "https://connectmq.com/data-centers/" language: "en" --- Data Center Monitoring # MQTT for Data Center Monitoring PDUs, cooling units, UPS systems and rack sensors report power, temperature and humidity across every hall and site. Edge gateways publish those values once over MQTT, and your DCIM, NOC alerting and energy reporting each subscribe to what they need. [Try it free](https://app.connectmq.com/signup) [Quickstart](https://connectmq.com/developers/) No card required What you can build ## Build your data center monitoring on ConnectMQ You build the DCIM views, alerts and reports, ConnectMQ moves the data. Edge gateways in each hall read PDUs, cooling units, UPS systems and rack sensors and publish on change; your DCIM, capacity planning, NOC alerting and energy reporting each subscribe in parallel. Your BMS stays in control of the equipment. Your halls and sites **Rack PDUs**dc/{site}/{hall}/rack-{id}/pdu/power **CRAC / CRAH units**dc/{site}/{hall}/crac-{id}/state **Rack temperature & humidity**dc/{site}/{hall}/rack-{id}/env **UPS systems**dc/{site}/ups-{id}/status **ConnectMQ** - TLS on 8883 - per-device ACL - threshold alerts - retained messages What you build on top **DCIM dashboards** **Capacity planning** **NOC alerting** **Energy & PUE reporting** What you get ## Data Center Monitoring on ConnectMQ - Power, cooling and rack environment data from every hall on one broker - Published on change — no central poller hammering every device - Retained last values, so a new dashboard is complete straight away - Separate credentials and topic permissions for every site example topic design ``` dc/dfw1/hall-b/rack-b14/env dc/dfw1/hall-b/rack-b14/pdu-a/power dc/dfw1/hall-b/crac-02/state (retained) ``` Report by exception ## Stop polling every PDU and CRAC The usual set-up is a collector at each site that polls every PDU, cooling unit and UPS over SNMP or Modbus, every minute or so, whether anything changed or not. With ConnectMQ, an edge gateway in each hall still reads the equipment locally but publishes only when a value changes — and every system that needs it subscribes. ### On-site collectors polling - Every PDU, CRAC and UPS is polled on a fixed cycle - A hot spot waits for the next poll before anyone sees it - Each new tool adds another poller or another export - Every site’s data sits in its own collector ### ConnectMQ - Edge gateways publish on change, over TLS - DCIM, NOC alerting and reporting all subscribe to the same topics - Retained last values and rules & alerts on the broker - Per-site credentials and topic permissions Real-life example ## Cool down a hot spot before the servers throttle A common data center MQTT setup: an edge gateway in the hall publishes rack temperatures on change, the DCIM in the NOC subscribes, and the site’s BMS gateway listens for cooling setpoints. Hall and NOC both connect out to ConnectMQ over TLS; the BMS stays in charge of the cooling units. Data hall B → ConnectMQ → Operations centre. Reads the rack sensors on the local network and publishes only when a value changes: rack B-14’s inlet air has reached 31.2 °C. Subscribed to every hall through ConnectMQ. Its rule for inlets above 27 °C opens incident INC-2291 and requests an 18 °C supply-air setpoint on CRAC-02. The only client allowed to write to hall B’s cooling: it applies the setpoint over BACnet, CRAC-02 raises its fan to 85 % and the gateway publishes the new state. Gets the NOC notification with the values. A few minutes later rack B-14 is back at 26.4 °C, and the incident shows every step.ConnectMQMQTT broker · TLS 8883Incident INC-2291 openedHALL B · B-1424.1 °C31.2 °C ▲28.4 °C ▼INC-2291CRAC-02 18 °COperations centreDCIM · subscribed to every hallCold aisleHALL BB-12B-13B-14B-15B-14 · Inlet24.1 °C27.8 °C31.2 °C28.4 °C26.4 °C20 °C18 °C45 %85 %CRAC-02EDGE-BBMS-BBACnetData hall BEdge gateway + BMS gatewaydc/dfw1/hall-b/rack-b14/env {"inlet":31.2}dc/dfw1/hall-b/rack-b14/env {"inlet":31.2}dc/dfw1/hall-b/crac-02/set {"supply":18}dc/dfw1/hall-b/crac-02/set {"supply":18}dc/dfw1/hall-b/crac-02/state {"supply":18,"fan":85}NOC alerts · nowRack B-14 at 31.2 °C — CRAC-02 set to 18 °CData hall B → ConnectMQ → Operations centre. Reads the rack sensors on the local network and publishes only when a value changes: rack B-14’s inlet air has reached 31.2 °C. Subscribed to every hall through ConnectMQ. Its rule for inlets above 27 °C opens incident INC-2291 and requests an 18 °C supply-air setpoint on CRAC-02. The only client allowed to write to hall B’s cooling: it applies the setpoint over BACnet, CRAC-02 raises its fan to 85 % and the gateway publishes the new state. Gets the NOC notification with the values. A few minutes later rack B-14 is back at 26.4 °C, and the incident shows every step.ConnectMQMQTT broker · TLS 8883Incident INC-2291 openedHALL B · B-1424.1 °C31.2 °C ▲28.4 °C ▼INC-2291CRAC-02 18 °COperations centreDCIM · subscribed to every hallCold aisleHALL BB-12B-13B-14B-15B-14 · Inlet24.1 °C27.8 °C31.2 °C28.4 °C26.4 °C20 °C18 °C45 %85 %CRAC-02EDGE-BBMS-BBACnetData hall BEdge gateway + BMS gatewaydc/dfw1/hall-b/rack-b14/env {"inlet":31.2}dc/dfw1/hall-b/rack-b14/env {"inlet":31.2}dc/dfw1/hall-b/crac-02/set {"supply":18}dc/dfw1/hall-b/crac-02/set {"supply":18}dc/dfw1/hall-b/crac-02/state {"supply":18,"fan":85}NOC alerts · nowRack B-14 at 31.2 °C — CRAC-02 set to 18 °C 1. 03:14 **Edge gateway in hall B** Reads the rack sensors on the local network and publishes only when a value changes: rack B-14’s inlet air has reached 31.2 °C. `dc/dfw1/hall-b/rack-b14/env → {"inlet":31.2,"rh":38}` 2. 03:14 **DCIM in the NOC** Subscribed to every hall through ConnectMQ. Its rule for inlets above 27 °C opens incident INC-2291 and requests an 18 °C supply-air setpoint on CRAC-02. `dc/dfw1/hall-b/crac-02/set → {"supply":18}` 3. 03:15 **BMS gateway → CRAC-02** The only client allowed to write to hall B’s cooling: it applies the setpoint over BACnet, CRAC-02 raises its fan to 85 % and the gateway publishes the new state. `dc/dfw1/hall-b/crac-02/state → {"supply":18,"fan":85}` 4. 03:21 **On-call engineer** Gets the NOC notification with the values. A few minutes later rack B-14 is back at 26.4 °C, and the incident shows every step. **When a new NOC screen connects,** it subscribes to `dc/dfw1/hall-b/+/env` and gets every rack’s last reading at once — the edge gateway publishes every reading with the retain flag, so nothing waits for the next change. [Python code sample](https://connectmq.com/code-samples/python/) [Node-RED flow](https://connectmq.com/code-samples/node-red/) Platform ## Features that help with Data Center Monitoring [ ### Dashboard & monitoring Live topic cards, signals and ISA-95 workspace Learn more](https://connectmq.com/monitoring/)[ ### Rules & alerts Threshold rules, alert log and notifications Learn more](https://connectmq.com/rules-alerts/)[ ### Digital Twin Your factory in 3D with live MQTT telemetry Learn more](https://connectmq.com/digital-twin/) Solutions ## Other ways teams use ConnectMQ [ ### Industrial IoT & Smart Manufacturing Machines, PLC gateways, OEE and quality data ](https://connectmq.com/industrial-iot/)[ ### Smart Home Hubs, sensors and Home Assistant setups ](https://connectmq.com/smart-home/)[ ### Fleet Telematics Vehicle tracking, telematics and cold chain ](https://connectmq.com/fleet-logistics/)[ ### Smart Energy Meters, EV chargers, solar and batteries ](https://connectmq.com/energy-utilities/)[ ### Connected Products & Smart Hardware Smart devices you ship to your own customers ](https://connectmq.com/connected-products/)[ ### Connected Robots & Physical AI Robot fleets talking to fleet managers and AI pipelines ](https://connectmq.com/robotics/)[ ### Smart City Streetlights, parking, air and waste sensors ](https://connectmq.com/smart-city/)[ ### Smart Agriculture Soil probes, weather stations and irrigation ](https://connectmq.com/smart-agriculture/)[ ### Prototyping & Education From first ESP32 to classroom labs ](https://connectmq.com/prototyping-education/) Industries & use cases ## Where teams use Data Center Monitoring ### Industries - [Healthcare](https://connectmq.com/industries/healthcare/) - [Telecom](https://connectmq.com/industries/telecom/) - [Financial Services](https://connectmq.com/industries/financial-services/) ### Use cases - [Cleanroom & GMP Environmental Monitoring](https://connectmq.com/use-cases/cleanroom-environmental-monitoring/) - [ATM & POS Terminal Monitoring](https://connectmq.com/use-cases/atm-pos-terminal-monitoring/) - [Telecom Network Equipment Monitoring](https://connectmq.com/use-cases/network-equipment-monitoring/) Pilot ## Pilot one data hall this week Start on the Free plan with no card. Basic covers up to 100 concurrent connections — enough for the edge and BMS gateways of a few halls and the systems that subscribe to them. Move to Scale when you add sites. [Start for free](https://app.connectmq.com/signup) [See pricing](https://connectmq.com/pricing/) ## Articles [All articles](https://connectmq.com/blog/) Industrial IoT ### [Sparkplug B and the Unified Namespace: Structuring Industrial IoT Data on MQTT](https://connectmq.com/blog/mqtt-sparkplug-b-unified-namespace/) Sparkplug B gives industrial MQTT a strict session and payload model, while a Unified Namespace gives your plant data a single, readable home. Here is how they fit together, with topic design tips and live examples. August 26, 20269 min read Managed MQTT Cloud ### [How to Choose an IoT MQTT Broker: 12 Criteria and the Questions to Ask Your Vendor](https://connectmq.com/blog/how-to-choose-an-iot-mqtt-broker/) A practical 12-point checklist for choosing an IoT MQTT broker, a table of questions to ask every vendor, and a five-minute hands-on test you can run against broker.connectmq.com. September 21, 20269 min read MQTT Security ### [MQTT Security Best Practices: A 12-Point Checklist for IoT Teams](https://connectmq.com/blog/mqtt-security-best-practices/) A hands-on MQTT security checklist covering TLS, credentials, client IDs, topic design, payload validation, rate limits and certificate checks, plus how ConnectMQ handles each point. September 28, 202611 min read