Jan-Otto Kröpke
Jan-Otto Kröpke
I feel that current behavior is fine. If windows report no value, the exporter should not fake a value.
Thermalzone has similiar issues. Win32_Sensor ist most of the time empty, too. Feels like Microsoft create some generic solutions, but no hardware vendor implement them.
Hi @dkrdj I'm currently removing all dependencies against WMI, if possible. Is there an Win32 API replacement? And I'm currently not sure, which collector should do it.
Yes, potential memory leaks and performance issues are the reasons, because we have around 20+ collectors and it's not possible to query WMI in parallel.
So in total, it doesn't make sense to include that collector?
What about pass credentials to windows exporter and collector may initiate connections on they own?
https://learn.microsoft.com/de-de/windows/win32/api/fileapi/nf-fileapi-getdiskfreespaceexw does not need a drive. It could connect to an UNC path directly. Instead monitor local Network drives, monitor remote shares directly.
Yeah, timeout management with sync blocking syscalls is not easy.
If you already have to use scripts for that setup, I would recommend to use an script to collect metrics and use the textfile collector in windows_exporter. From maintainer perspective,...
Is #830 still relevant?