Technical Preview
windows_exporter is undergoing a modernization. We plan to deliver a stable release by mid-2025, with upcoming changes—including a newly designed Hyper-V collector—adding value to the official 1.0 stable release.
Windows Management Infrastructure (MI) as a Replacement for Windows Management Instrumentation (WMI)
As of version 0.30.0, windows_exporter no longer uses WMI directly. Instead, it utilizes its successor, Windows Management Infrastructure (MI), available since Windows Server 2012. MI offers several advantages, such as the ability to run queries in parallel.
Performance Data Helpers
windows_exporter 0.30 uses Performance Data Helpers instead grab and parse the binary data from the registry. This change also introduces support for Process V2, which is enabled by default on Windows Server 2022. In conclusion, the code from https://github.com/leoluk/perflib_exporter is removed.
💥 Breaking Changes
windows_exporter introduced an other wave of breaking changes. Sorry for that! The reason is that there is not enough maintainer capacity to hold backwards compatibility. Keep in mind, windows_exporter is using semver as versioning strategy and below version 1, backwards compatibility is not necessary.
On plan, this might be the last wave of breaking changes. All modernization steps are done and we are now looking for a stabilization and bug fixes phrase for now.
What's Changed
💥 Breaking Changes
- hyperv: Refactor collector, added DataStore, Virtual SMB and Dynamic Memory Balancer metrics (click PR number for more information) by @jkroepke in #1712
✨ Exciting New Features
- mssql: expose server version info by @jkroepke in #1741
- exchange: Extend Transport Queue metrics by @jkroepke in #1749
🐞 Bug Fixes
- logicaldisk: fix base counter values by @jkroepke in #1747
- logical_disk: Get Volume ID for NTFS Volume Mounts by @jkroepke in #1752
- mssql: fix performance counter with additional server instance by @jkroepke in #1753
Full Changelog: v0.30.0-beta.3...v0.30.0-beta.4