transform beat.cgroup.memory.mem.usage.bytes to Gauge

[boranx]

What does this PR do?

This transforms beat.cgroup.memory.mem.usage.bytes to Gauge as it can have a negative value

Why is it important?

it tries to eliminate Non-zero metrics in the last 30s errors by transforming beat.cgroup.memory.mem.usage.bytes to gauge

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
• I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

Author's Checklist

• [ ]

How to test this PR locally

Related issues

Fix: #31582

Use cases

Screenshots

Logs

[cla-checker-service]

💚 CLA has been signed

[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: 2022-08-10T18:36:55.652+0000

• Duration: 87 min 37 sec

Test stats 🧪

Test	Results
Failed	0
Passed	22559
Skipped	1937
Total	24496

💚 Flaky test report

Tests succeeded.

🤖 GitHub comments

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

• /test : Re-trigger the build.

• /package : Generate the packages and run the E2E tests.

• /beats-tester : Run the installation tests with beats-tester.

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

[elasticmachine]

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

[cmacknz]

Changes look good, you'll need to sign the CLA and then we can kick the tests and get this merged.

[boranx]

I'd bet I've signed this a couple of hours ago, but in order to reflect the changes, should we re-trigger ci?

/test

[cmacknz]

/test

[cmacknz]

Yes, CLA check has passed now. Someone from Elastic has to trigger the first test run, which I've now done.

We can ignore the linter errors here as they aren't caused by changes you've made (it always wants to lint the entire file, not just the changed lines).

[cmacknz]

Merged, thanks!