-
Notifications
You must be signed in to change notification settings - Fork 676
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Time metrics #532
Comments
Seems like an excellent addition. Are there performance counters we could read via perflib instead of WMI? |
Aren't these performance counters? I mean I can also find them in the performance monitor.
|
Most of the time there's a one-to-one mapping (and the main challenge is finding the mapping), but WMI also exposes a some stuff which doesn't have counters. So, nice that they are there. It is a lot more efficient to work with the counters rather than doing WMI queries, so we try to avoid adding new WMI classes (and are slowly converting existing collectors to use counters directly). |
I would very much like to see this available very soon. What's the next step to make this happen? |
Well, the absolutely fastest way would be if you would be able to contribute the collector. The |
@tahachoura could you open an issue for this please? |
Since node_exporter has time metrics, why does wmi_exporter not have them yet?
I've found
Win32_PerfRawData_MicrosoftWindowsW32TimePerf_WindowsTimeService
which has the following data:The only thing stopping me from generating a collector is that the most important metric
ComputedTimeOffset
is aulong
, which is a 64-bit integer. (https://docs.microsoft.com/en-us/dotnet/visual-basic/language-reference/data-types/ulong-data-type)The text was updated successfully, but these errors were encountered: