You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Windows_exporter is undergoing 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), which has been available since Windows Server 2012. MI offers several advantages, such as the ability to run queries in parallel.
New Docker Base Images for Kubernetes Clusters
Windows_exporter is now using a specialized base image designed for host process pods. The image size has been reduced from hundreds of MBs to just 10 MB. Support for Windows Server 2025 has also been added.
Performance Data Helpers
Windows_exporter 0.30 now uses Performance Data Helpers instead of grabbing and parsing binary data from the registry. This change also introduces support for Process V2, which is enabled by default on Windows Server 2022. As a result, the code from leoluk/perflib_exporter has been removed.
💥 Breaking Changes
Windows_exporter introduces another wave of breaking changes. Apologies for the inconvenience! The reason for these changes is that there is not enough maintainer capacity to maintain backward compatibility. Please keep in mind that windows_exporter uses semver as its versioning strategy, and backward compatibility is not required for versions below 1.0.
This may be the last wave of breaking changes. All modernization steps have been completed, and we are now focused on stabilization and bug fixes.
The text was updated successfully, but these errors were encountered:
Looking for 0.30.0 Beta Testers!
After a month of work, the 0.30.0 branch finally includes all the planned features. We've improved scrape times and reduced CPU usage to a minimum.
Download the Latest v0.30.0
👉 v0.30.0-rc.0 Release
Technical Modernization
Windows_exporter is undergoing 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), which has been available since Windows Server 2012. MI offers several advantages, such as the ability to run queries in parallel.
New Docker Base Images for Kubernetes Clusters
Windows_exporter is now using a specialized base image designed for host process pods. The image size has been reduced from hundreds of MBs to just 10 MB. Support for Windows Server 2025 has also been added.
Performance Data Helpers
Windows_exporter 0.30 now uses Performance Data Helpers instead of grabbing and parsing binary data from the registry. This change also introduces support for Process V2, which is enabled by default on Windows Server 2022. As a result, the code from leoluk/perflib_exporter has been removed.
💥 Breaking Changes
Windows_exporter introduces another wave of breaking changes. Apologies for the inconvenience! The reason for these changes is that there is not enough maintainer capacity to maintain backward compatibility. Please keep in mind that windows_exporter uses semver as its versioning strategy, and backward compatibility is not required for versions below 1.0.
This may be the last wave of breaking changes. All modernization steps have been completed, and we are now focused on stabilization and bug fixes.
The text was updated successfully, but these errors were encountered: