Releases: prometheus-community/windows_exporter
v0.14.0
Enhancements
- Add
run_as
label onwindows_service_info
(#527, thanks @paologallinaharbur!) - Expose exporter version information on /version (#555, thanks @zlepper!)
- Convert MSSQL collector to use perflib rather than WMI (#592, thanks @mallenLF!)
- Add FSRM collector (#437, thanks @nwies!)
Bug fixes
Docs
Thanks to @JDA88, @zlepper, @clain23 and @eloekset for fixes and updates on the documentation since the last release!
v0.13.0
Breaking changes
Project renamed and moved
The exporter has been renamed to windows_exporter, and moved to the prometheus-community organization (see #519).
This includes changing the metrics' name prefixes from wmi_
to windows_
, meaning that all queries need to be changed to match the new names.
For example, windows_cpu_time_total
replaces wmi_cpu_time_total
.
There are no functional changes in this release.
v0.12.0
Deprecation note
This is the last planned release with the wmi_exporter
name, future releases will be named windows_exporter
. See #499 and #519 for context.
This also means that the next release will have a breaking change, the metrics will change names from wmi_...
to windows_...
. You will need to adjust your dashboards and alerts. See this comment for a suggestion if you want to rename metrics already now.
Enhancements
- New collector:
terminal_services
(#491, thanks @asiyani!) - New collector:
remotefx
(#491, thanks @asiyani!) - New collector:
dhcp
(#493, thanks @breed808!) - New collector:
exchange
(#508, thanks @rmyhren and @eikaas!) - Add wmi_service_info metric with display_name and pid labels (#516, thanks @gsanchezgavier!)
Bug fixes
- Exporter now gives an error message instead of crashing if a non-existing collector is specified in
--collectors.enabled
(#529) - Collector generator now works with Powershell 7 (#523, thanks @basroovers)
v0.11.1
v0.11.0
Breaking changes
- We no longer redirect all paths to /metrics (#473). This means that if you configured Prometheus to scrape eg /not-metrics but did not configure wmi_exporter to expose the metrics on this port (using the
--telemetry.path
flag), your scrapes will now fail with a http 404. Make sure your Prometheus job configuration and the exporter configuration matches! - The
--collector.process.processes-where
flag has been removed, in favour of--collector.process.whitelist
and--collector.process.blacklist
(see more below)
Enhancements
- The
process
collector has been rewritten to use perflib (#489), yielding significant performance improvements. Since it no longer uses WMI, the filtering mechanism can no longer use WQL. It now instead uses a white- and blacklist with regular expressions, like several other collectors. - We now limit how many concurrent scrapes are allowed (#474). The exporter will only accept a limited number (by default 5) requests to be processed simultaneously. A flag
--max-requests
can be used to tune this. Typically, running several simultaneous scrapes tends to make the WMI subsystem slow.
v0.10.2
v0.10.1
v0.10.0
Enhancements
- Add
wmi_os_info
metric with information about Windows product name and version (#413, thanks @der-eismann!) - Add
wmi_cs_hostname
metric with hostname, domain and fqdn info (#470, thanks @sll552!) - Only query the perflib objects we need, improving performance and resolving some very slow queries on Exchange servers (#461)
Bug fixes
v0.9.0
Enhancements
- ADFS collector (#399, thanks @breed808!)
- The
logical_disk
,memory
,net
andsystem
collectors now use perflib rather than WMI (#400, #402, #403, #405, thanks @breed808!)
Bug fixes
wmi_tcp_connections_established
is now correctly a gauge, rather than a counter (#411, thanks @breed808!)
Documentation
Thanks @charlesmorin, @floptical and @Schlump for documentation updates since the last release!