add metrics logging to beat receivers

[leehinman]

Proposed commit message

Add MakeReporter to beat receivers start up. This will produce the
"Non-zero metrics in the last 30s" in the logs. Also added the Stop
function to the beat receiver shutdown

This is necessary so the metrics will end up in the elastic-agent
diagnostics output.

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

• This will produce logs that were not being produced before

Author's Checklist

• [ ]

How to test this PR locally

Integration tests

cd x-pack/filebeat/fbreceiver && go test .
cd x-pack/metricbeat/mbreceiver && go test .

In elastic-agent

1. Build elastic-agent with this PR
2. Install elastic-agent with system integration
3. allow agent to run for at least 30 seconds
4. jq -r 'select (.message == "Non-zero metrics in the last 30s") | .component.id' *.ndjson | sort -u in logs directory

You should see that every component is producing it's own 30s metrics log entries

Related issues

• Relates [beat receivers] no 30s metrics in the logs with otel runtime elastic-agent#12380

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 @leehinman? 🙏.
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.

[elasticmachine]

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

[mauri870]

LGTM, nothing stands out aside from the already existing comments.