remove otel.component.id and otel.component.kind fields from beat receivers

[leehinman]

Proposed commit message

remove otel.component.id and otel.component.kind from events that were generated by beat receivers.

The cost of sending the extra data in every event was found to be not worth the value of having the fields.

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

If anyone was using the fields to track beat receiver events, they won't be available anymore. However, the fields we not documented publicly and were not part of an API.

Author's Checklist

• [ ]

How to test this PR locally

cd x-pack/filebeat/fbreceiver
go test .

cd x-pack/metricbeat/mbreceiver
go test .

cd x-pack/libbeat/outputs/otelconsumer
go test .

Related issues

• Closes [beats receivers] Remove collector component identifying fields #47600

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)

[khushijain21]

LGTM

[pierrehilbert]

@narph Could we have your approval here please?

[mergify]

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b 47600_remove_collector_fields upstream/47600_remove_collector_fields
git merge upstream/main
git push upstream 47600_remove_collector_fields

[pierrehilbert]

@efd6 / @andrewkroh could you please take a look here?

[mauri870]

Thanks. The cost of having these fields turned out to be higher than I initially anticipated when I proposed them. Looking at it from a different perspective now, I believe that if we ever want something like this back, Elastic Agent should probably be the one responsible for adding them.