[Windows] Added support for custom processors on perfmon

[philippkahr]

What does this PR do?

Adds support for the custom processor definition in windows perfmon.

Checklist

• I have reviewed tips for building integrations and this pull request is aligned with them.
• I have added an entry to my package's changelog.yml file.

[elasticmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2023-01-23T19:49:28.853+0000

• Duration: 16 min 27 sec

Test stats 🧪

Test	Results
Failed	0
Passed	129
Skipped	0
Total	129

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

[elasticmachine]

Pinging @elastic/elastic-agent (Team:Elastic-Agent)

[elasticmachine]

Pinging @elastic/security-external-integrations (Team:Security-External Integrations)

[andrewkroh]

There needs to be a change to the config file to utilize these processors you added to the manfiest.

perfmon/agent/stream/stream.yml.hbs:

{{#if processors}}
processors:
{{processors}}
{{/if}}

[philippkahr]

@andrewkroh somehow I am still missing something?

[andrewkroh]

The version contained in the windows/manifest.yml needs updated to 1.15.3. CI is complaining about:

[2023-01-19T12:54:34.746Z] Error: checking package failed: linting package failed: found 1 validation error:

[2023-01-19T12:54:34.746Z]    1. current manifest version doesn't have changelog entry

I would say this is a new feature rather than a bug fix so using 1.16.0 would be more appropriate under semver.org rules.

[philippkahr]

Would love to know what I did wrong. I added 1.15.3 back then and now changed it to 1.16, but it still error with:

[2023-01-20T09:31:58.481Z] Error: checking package failed: linting package failed: found 1 validation error:
[2023-01-20T09:31:58.481Z]    1. current manifest version doesn't have changelog entry

[andrewkroh]

I think there's a check the verifies that the latest changelog entry matches the version contained in the manefest.yml. So until those two values are the same we will get this type of error.

[elasticmachine]

🌐 Coverage report

Name	Metrics % (covered/total)	Diff
Packages	100.0% (4/4)	💚
Files	87.5% (7/8)	👎 -12.5
Classes	87.5% (7/8)	👎 -12.5
Methods	83.516% (76/91)	👎 -16.484
Lines	92.714% (5039/5435)	👍 10.559
Conditionals	100.0% (0/0)	💚

[andrewkroh]

@elastic/elastic-agent-data-plane As the package owner, are you good with these changes?

[leehinman]

LGTM

[elasticmachine]

Package windows - 1.16.0 containing this change is available at https://epr.elastic.co/search?package=windows