Enrich otel logs to match beat process logs

[khushijain21]

What does this PR do?

This PR adds component.* fields for components run by the OTelManager. For more reasoning check https://github.com/elastic/ingest-dev/issues/5139

Checklist

• I have read and understood the pull request guidelines of this project.
• 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/fragments using the changelog tool
• I have added an integration test or an E2E test

How to test this PR locally

Logs from normal mode

{"log.level":"info","@timestamp":"2025-02-24T10:59:43.243Z","message":"X","component":{"binary":"filebeat","dataset":"elastic_agent.filebeat","id":"filestream-monitoring","type":"filestream"},"log":{"source":"filestream-monitoring"},"log.logger":"centralmgmt.V2-manager","log.origin":{"file.line":505,"file.name":"management/managerV2.go","function":"github.com/elastic/beats/v7/x-pack/libbeat/management.(*BeatV2Manager).unitListen"},"service.name":"filebeat","ecs.version":"1.6.0","ecs.version":"1.6.0"}

Logs from components run by Otel Manager

{"log.level":"error","@timestamp":"2025-02-27T17:24:15.152+0530","log.logger":"modules","message"X","log":{"source":"elastic-agent"},"kind":"receiver","name":"filebeatreceiver/_agent-component/filestream-default","data_type":"logs","log":{"source":"filestream-default"},"component":{"binary":"filebeat","dataset":"elastic_agent.filebeat","id":"filestream-default"},"service.name":"Khushis-MacBook-Pro.local","ecs.version":"1.6.0","ecs.version":"1.6.0"}

Some Differences:

• We have two log.source fields in the latter. It is not misleading, but two fields with same key can be confusing to users.

Related issues

• Closes https://github.com/elastic/ingest-dev/issues/5139

[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 withfields upstream/withfields
git merge upstream/main
git push upstream withfields

[mergify]

This pull request does not have a backport label. Could you fix it @khushijain21? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-./d./d is the label that automatically backports 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-control-plane (Team:Elastic-Agent-Control-Plane)

[swiatekm]

LGTM, had two minor questions.

[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 withfields upstream/withfields
git merge upstream/main
git push upstream withfields

[elastic-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube

[elasticmachine]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: c96d478

Failed CI Steps

• Packaging: windows/amd64 zip
• Win2022:sudo:upgrade
• Win2025:sudo:upgrade
• x86_64:sudo: upgrade
• arm:sudo: upgrade

History

• 💚 Build #18449 succeeded d9db1f3
• 💔 Build #18434 failed f17feea
• 💛 Build #18297 was flaky a2204bf
• 💔 Build #18296 failed 5441a20
• 💔 Build #18294 failed 9e557a4
• 💔 Build #17631 failed 67dca93

cc @khushijain21

[cmacknz]

This should be in 9.0 as well eventually (after release). I've added the backport PR so we don't forget about his.