windows_exporter: Thermalzone not working

Hi,

My exporter does not expose any metrics regarding the thermalzone. It is enabled however:

windows_exporter_collector_duration_seconds{collector="thermalzone"} 0.0060052
windows_exporter_collector_success{collector="thermalzone"} 1
windows_exporter_collector_timeout{collector="thermalzone"} 0

[System.Environment]::OSVersion.Version

Major  Minor  Build  Revision
-----  -----  -----  --------
10     0      19042  0

Exporter version: Starting windows_exporter (version=0.16.0, branch=master, revision=f316d81d50738eb0410b0748c5dcdc6874afe95a)

I run windows exporter with the following arguments: "C:\Program Files\windows_exporter\windows_exporter.exe" --log.format logger:eventlog?name=windows_exporter --telemetry.addr :9182 --collectors.enabled cpu,cs,logical_disk,logon,memory,net,os,process,service,system,tcp,time,thermalzone,textfile

I’m a Linux engineer, so I have no clue how to troubleshoot something like this. Please advice, thank you!

About this issue

Original URL
State: open
Created 3 years ago
Reactions: 5
Comments: 28 (8 by maintainers)

Most upvoted comments

Yes, there’s two issues with the collector that have been raised in this thread:

Unknown dependency preventing thermalzone collector and Perflib commands from returning metrics
Translated name of Thermalzone ListSet preventing collector from working correctly on non-English locales.

Users in this thread are largely experiencing 1), but 2) is also a problem.

breed808 on Feb 12, 2022

I think a separate yet related issue here is that windows_exporter_collector_success{collector="thermalzone"} 1 should be 0.

rlabrecque on Aug 13, 2021

The translated ListSet names dont’t match the English name in the collector.

From the previous reports I’ve seen on this issue, not all ListSets have translation problems (or are not translated). It’s something we should address at some stage, else we’re excluding entire localizations from running the exporter.

breed808 on Feb 12, 2022