[iis][windows] Adds cpu number information to IIS module and Windows perfmon dataset

[giorgi-imerlishvili-elastic]

Proposed commit message

Adds cpu number information to IIS module and Windows perfmon dataset
Purpose of this change is to help customers have better view on CPU performance. For example with IIS module customer is able to see CPU load but currently it doesn't have ability to show how many CPU are there in total. This sometimes might lead to confusion because currently CPU load is provided with percents where maximum percent cap is calculated via this formula: from 0 through 100 * ProcessorCount (source: https://learn.microsoft.com/en-us/windows/win32/perfctrs/collecting-performance-data). So when someone sees for example CPU load: 155% without knowing CPU number, they won't be able to calculate cap.

Checklist

• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have made corresponding change to the default configuration files
• I have added tests that prove my fix is effective or that my feature works. Where relevant, I have used the stresstest.sh script to run them under stress conditions and race detector to verify their stability.
• I have added an entry in ./changelog/fragments using the changelog tool.

Disruptive User Impact

Author's Checklist

• [ ]

How to test this PR locally

Related issues

• Relates #elastic/obs-integration-team/issues/805
• Relates #elastic/sdh-beats/issues/6791

Use cases

Screenshots

Logs

[github-actions]

🤖 GitHub comments

Just comment with:

• run docs-build : Re-trigger the docs validation. (use unformatted text in the comment!)

[mergify]

This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @giorgi-imerlishvili-elastic? 🙏.
For such, you'll need to label your PR with:

• The upcoming major version of the Elastic Stack
• The upcoming minor version of the Elastic Stack (if you're not pushing a breaking change)

To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-8./d is the label to automatically backport to the 8./d branch. /d is the digit
• backport-active-all is the label that automatically backports to all active branches.
• backport-active-8 is the label that automatically backports to all active minor branches for the 8 major.
• backport-active-9 is the label that automatically backports to all active minor branches for the 9 major.

[github-actions]

🔍 Preview links for changed docs

• docs/reference/metricbeat/exported-fields-iis.md
• docs/reference/metricbeat/metricbeat-metricset-iis-application_pool.md
• docs/reference/metricbeat/metricbeat-metricset-iis-webserver.md
• docs/reference/metricbeat/metricbeat-metricset-iis-website.md

[elasticmachine]

Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane)

[VihasMakwana]

@giorgi-imerlishvili-elastic Is there an open issue for this? If not, could you update PR description with "Why this change is required and what does it fix/enhance?"

[giorgi-imerlishvili-elastic]

@giorgi-imerlishvili-elastic Is there an open issue for this? If not, could you update PR description with "Why this change is required and what does it fix/enhance?"

Just added description and related issues

[VihasMakwana]

just a nit. LGTM otherwise

[jmikell821]

Just a couple of slight comments, thanks!

[jmikell821]

Suggested change

	: Number of CPUs host have
	: Number of CPUs the host has

[jmikell821]

Suggested change

	Number of CPUs host have
	Number of CPUs the host has

[github-actions]

✅ Vale Linting Results

No issues found on modified lines!

---

The Vale linter checks documentation changes against the Elastic Docs style guide.

To use Vale locally or report issues, refer to Elastic style guide for Vale.