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

Bug fixes

• ADFS collector was not registering correctly since 0.10.0, leading to failed scrapes (#506)

v0.11.0

Breaking changes

⚠️ This release has breaking changes! Make sure to read and understand the below before upgrading!

• 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

Bug fixes

• The version information is now properly written into the binary (#480)

v0.10.1

Bug fixes

• Fix cs collector crashing on domain joined machines (#476, thanks @sll552!)

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

• Fix mssql collector ratio metrics (#463, thanks @secustor!)

v0.9.0

Enhancements

• ADFS collector (#399, thanks @breed808!)
• The logical_disk, memory, net and system 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!

v0.8.3

Bug fixes

• wmi_net_current_bandwidth is now correctly a gauge, instead of a counter (#393, thanks @breed808!)

v0.8.2

Enhancements

• Latency metrics added to logical_disk metrics (#387, thanks @breed808!)
• logon collector for logon sessions (#384, thanks @breed808!)

Bug fixes

• container collector was not built into the binary (#391)

v0.8.1

Bug fixes

• Fix resource leak leading to slow increase in memory usage over time (#376)