[Windows integration] Perfmon dataset: staging_space_in_use tops out at 32-bit INT_MAX

[ycombinator]

For confirmed bugs, please report:

• Version: 8.9.2
• Operating System: Windows

The windows.perfmon.metrics.staging_space_in_use field seems to top out at 2147483647, which corresponds to the largest signed integer on 32-bit systems (2^31-1). Therefore, for systems that report larger values, the dataset reports incorrect data.

[ycombinator]

Is the fix for this issue simply for users to specify format: large for the staging_space_in_use field in the dataset's configuration? For example:

metricsets:
    - perfmon
perfmon.queries:
    - counters:
      - field: staging_space_in_use
        format: long
        name: Staging Space In Use

Or is a fix needed in the dataset's implementation?

[Erikg346]

Hey @ycombinator ,
Specifying format: large works to get the correct value!

[botelastic]

Hi!
We just realized that we haven't looked into this issue in a while. We're sorry!

We're labeling this issue as Stale to make it hit our filters and make sure we get back to it as soon as possible. In the meantime, it'd be extremely helpful if you could take a look at it as well and confirm its relevance. A simple comment with a nice emoji will be enough :+1.
Thank you for your contribution!