Guides
Liquid-cooling water quality monitoring for data centers
What should be monitored in a liquid-cooling water loop?
A practical monitoring plan starts with coolant temperature, pressure and flow, then adds conductivity, pH, dissolved oxygen, turbidity or particle indicators where the coolant specification and materials require them. Leak detection and trend alarms should be tied to the operating limits agreed for the project, not copied from an unrelated system.
Define each loop before selecting instruments
Document the technology-cooling loop and facility-water loop separately. Record coolant chemistry, wetted materials, normal and maximum temperatures, pressure, flow, pipe size, sampling point, control interface and maintenance access.
Information required for a monitoring proposal
Send the server or rack platform, CDU model or duty, coolant specification, loop diagram, operating ranges, required parameters, alarm philosophy, communications protocol and destination. FUNEL can then review the CDU boundary together with a model-specific instrumentation proposal.
Review liquid-cooling water-quality instrumentation →
Common questions
What should be monitored in a liquid-cooling water loop?
Start with temperature, pressure and flow. Add other parameters only where coolant, materials and risk review require them.
Can one sensor package be used for every project?
No. Coolant chemistry, materials, operating range and interfaces must be reviewed for each loop.
Does online monitoring replace coolant sampling?
Not automatically. Online trends and laboratory or manual checks serve different purposes.
Final configuration, performance, applicable requirements and delivery are defined in the agreed project specification.
Discuss your project
