Rich Siegel

the nil/err fixes, and commenting import "github.com/prometheus-community/windows_exporter/log" worked. snip from localserver:9182/metrics ``` # HELP windows_msft_mpcomputerstatus_antispyware_signature_age (AntispywareSignatureAge) # TYPE windows_msft_mpcomputerstatus_antispyware_signature_age gauge windows_msft_mpcomputerstatus_antispyware_signature_age 0 # HELP windows_msft_mpcomputerstatus_antivirus_signature_age (AntivirusSignatureAge) # TYPE windows_msft_mpcomputerstatus_antivirus_signature_age gauge...

so I wonder if the right way to handle the version numbers of the components is like this: https://medium.com/teamzerolabs/staying-on-track-of-aging-node-packages-with-monitoring-in-prometheus-f915540e72df or https://www.robustperception.io/exposing-the-software-version-to-prometheus Not sure how to work this in...

Delayed here too, due to other constraints. No worries. The numbers are actually correct despite looking suspicious, because I was testing on a well updated endpoint, that never ran a...

win32_bios is the class in powershell gwmi win32_bios |fl *

I'm submitting a PR to get deprecated of this ill formed rule. It is bad for the community and people are abusing the rationale 'aliases are bad' instead of embracing...

> Times have moved on since this issue was created. True but in the duration this issue has caused irreparable harm to the ecosystem in favor of removing aliases from...

It's hardly cryptic. It's idiomatic. If anything the rule should be reversed. Anyone who endorses or uses Foreach-object should use %. foreach is not even a legit verb or word...

Whitelist common aliases from a rule that discourages use? This is backwards. If you want to block a particular alias then you should cite a reason such as incompatibility across...

I have moved on... while this exporter is extremely performant on some things due to great optimizations, it is difficult to customize w/o recompiling for missing capabilities (ie in the...

side mention - https://github.com/hashicorp/terraform-provider-vsphere/pull/2017#issuecomment-1753832562