Abstract
Measuring software energy consumption is becoming essential, but doing it correctly is not straightforward. Energy is measured at the hardware level, while software operates at higher levels of abstraction, making attribution inherently uncertain. Here, we explore RAPL-based tools that bridge this gap, comparing their capabilities and limitations and providing practical guidance to help practitioners choose the right tools for experiments, monitoring, and production use.