Case study

rackpulse: modern health monitoring for 2016-era servers

Overview

rackpulse is a health monitoring and AI provisioning agent for legacy Dell PowerEdge servers running VMware ESXi 6.7. It backports the host and hardware health monitoring that modern platforms take for granted onto enterprise gear that's past its vendor's support window but still doing real work.

The problem

ESXi 6.7 hosts from the mid-2010s are everywhere, and they keep running because they're reliable. The problem is visibility. The tooling that used to watch this vintage is sunset, expensive, or abandoned, and the failure mode of old hardware is rarely sudden: temperatures climb, disks degrade, sensors go quiet. Without monitoring, those trends are invisible until something stops working.

The design: testable core, thin adapter

The architecture is the point of this project:

  • core.py is a pure decision engine: dataclasses and functions that take sensor readings and return health states with severity. No hardware imports, no I/O, fully unit-testable on any machine.
  • esxi.py is a thin adapter that talks to the host through pyVmomi and feeds readings into the core.

This split means the threshold logic, hysteresis, and escalation behavior are verified by tests that run in milliseconds, without a server in sight. The hardware layer is small enough to review by eye.

Key behaviors

  • Multi-tier severity. A warning at one threshold and a critical at the next are distinct events with distinct owners. Escalation is asserted in tests, not treated as a bug to smooth over.
  • AI provisioning agent. The agent plugs into the same core, so it inherits the same tested decision logic when it assesses host state and suggests provisioning actions.
  • Legacy as a first-class citizen. The project is explicit about its target: old enterprise gear, kept honest by modern monitoring. That's a real niche with real users.

Design decisions

  • Hardware-adjacent code must be testable without hardware. If the tests need a live server, they won't be run, and then the logic rots. This was the single most important decision in the project.
  • One platform, deeply. ESXi 6.7 with Dell iDRAC hardware. Narrow scope, done properly.
  • Homelab-first, production-relevant. Built against the same servers that run my workloads, so every feature is exercised by real use, not hypotheticals.

Result

Old servers with new visibility: temperature, disk, and host health trends that predict failure instead of reporting it. The same pattern, collect, decide, act, applied to the most stubborn hardware in the building.