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)

v0.8.0

Changes

This release brings some changes that you should be aware of when upgrading.

Timeouts

The exporter will now try to return within Prometheus timeout, even if all collectors have not yet finished. A new metric wmi_exporter_collector_timeout{collector="collector-name"} allows seeing when this happens.
The exporter does this by reading the scrape timeout automatically sent by Prometheus in the X-Prometheus-Scrape-Timeout-Seconds header, and subtracting a "safety margin" (default 0.5 seconds), then aborting when that time has passed. If your system is heavily loaded, you may need to increase this margin, and can do so with the new --scrape.timeout-margin flag.

Perflib

This release contains the first use of Perflib in the cpu collector to give a lower-overhead way of fetching data than WMI. If this works out well, we expect to convert a majority of the existing collectors to Perflib, which should alleviate a lot of the issues around WMI we've seen.

Enhancements

• More detailed CPU metrics on Windows 2008R2 and higher (#334, thanks @wizardmatas!)
• ThermalZone collector for reading system temperature (#359, thanks @StewartThomson!)
• SQL collector now exposes error counters (#370, thanks @callvirtual!)
• SQL collector now exposes transaction metrics (#372, thanks @callvirtual!)
• Convert cpu collector to perflib (#335)
• Timeout scrapes (#340)

Bugfixes

• MSMQ collector was logging erronously (#327, thanks @marek-vrana!)
• CPU usage metrics should be counters (#331, thanks @nbellowe!)
• MSSQL metric dbreplica_transaction_delay_seconds was reported in microseconds instead of seconds (#351, thanks @sqlkabouter!)

v0.7.999-preview

Changes

This is a preview release containing two changes we are considering:

• #335: Using raw performance counters rather than WMI, which will both yield significantly faster scrapes, as well as avoiding some bugs in Windows related to WMI hanging periodically (eg #89)
• #340: Aborting a scrape if there are stalls during the scrape, to ensure Prometheus gets a response even during high loads (#270)

Any feedback on these changes is very welcome as comments on the two above PRs!

About the version number

The Windows Installer framework requires a three-position version, and does not allow semver prerelease tags (-preview, in this case). It is also somewhat picky about which versions can be upgraded between. In order to both allow us to make patch releases on the 0.7 version, as well as support upgrading from this preview to a coming 0.8 release, patch number 999 was arbitrarily chosen.

v0.7.0

Enhancements

• Metrics for Windows Containers 🎉 (#320, thanks @sachinmsft!)

Other

• A discussion was had, and a decision was made (#321) to not enforce WMI-only collection of metrics. We hope this will open up new interesting possibilities going forward, such as the above Containers metrics!