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.

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

/test

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

cc: @qcorporation

@khushijain21 Please replace the link in the proposed commit message entry with text that is publicly meaningful in the context of a git log output.

cc: @nfritts

@khushijain21 could you address the linter warnings?

@swiatekm/ @andrzej-stencel can you provide your approval?