Releases: prometheus-community/windows_exporter
Releases · prometheus-community/windows_exporter
v0.3.2
New features
- Add metric for exporter start time,
process_start_time_seconds
(#194)
Bug fixes
- Having a legacy network adapter on a HyperV server would cause a crash (#193)
- Some counters in the system collector were exposed as gauges (#195)
v0.3.0
Breaking changes
This release has a breaking change in handling of command line flags. If you manage the flags passed to wmi_exporter yourself (rather than use the installer), you need to change from one dash to two (ie --collectors.enabled
, while previously it was -collectors.enabled
).
This change harmonizes the wmi_exporter with the rest of the Prometheus ecosystem, and also removes the need to quote flags in Powershell.
New features
- Textfile collector (#174)
- Service recovery options are set on installation, ensuring the exporter restarts if it crashes (#186)
Fixes
- All logs now end up in the Windows Event Log as intended (#183)
v0.2.10
net: export current_bandwidth, fixes #162
v0.2.9
New features
- Add TCP collector (#142)
- Add MSMQ collector (#159)
v0.2.8
Fix "no where-clause" warning in service collector. 2f7a372
Add .Net Performance counters. 809fe9b
fix collecting error with multiple IIS application worker processes. 105a1c8
Misc improvements
#109 - Service Collector Filter Flag
#100 - Add DisplayName and Description to Windows service
f4195aa - Conditional query for wmi fields added in IIS 8
v0.2.6
New features
AD: New collector for Active Directory server (#93)
Process: New collector for processes. Specify a filter with -collector.process.processes-where
to limit the processes returned. (#79)
Changes
scrape_duration_seconds
is now a gauge rather than a summary (#90)
v0.2.5
Bug fixes
This release fixes (#77) a memory leak on Windows Server 2016, or older versions which have upgraded to Windows Management Framework 5 or higher (commonly installed as the prerequisite for Powershell 5)
v0.2.4
Add Vmware collector (#81)