[beatreceiver] Do not require specifiying otelconsumer output

[khushijain21]

Proposed commit message

All beatreceivers will use otelconsumer output by default and it does not require us to specify this explicitly.

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

None

Related issues

• Relates [beats receivers] Do not require explicit configuration of the otelconsumer output #47656

[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 @khushijain21? 🙏.
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]

@khushijain21 Can you check if we need to clean up references to otelconsumer in libbeat/otelbeat/beatconverter/beatconverter_test.go? Also, do we need a similar cleanup task for elastic agent as well?

[mauri870]

LGTM

[khushijain21]

@khushijain21 Can you check if we need to clean up references to otelconsumer in libbeat/otelbeat/beatconverter/beatconverter_test.go? Also, do we need a similar cleanup task for elastic agent as well?

It is okay even if we specify otelconsumer output. I did not clean it up in beatconverter because we will eventually get rid of it anyway.

Yes, we should perform a similar cleanup task for elastic-agent as well though

[mauri870]

Yes, we should perform a similar cleanup task for elastic-agent as well though

Thanks for confirming! I see that you added a Closes comment, which should close the original issue. Mind creating one for elastic-agent? Keeping the original issue open also works for me, either way.

[leehinman]

LGTM. Thanks for the change.