Implement verifier receiver

[jeniawhite]

Summary

• Moves the verifier receiver from elastic/opentelemetry-collector-components into elastic-agent/internal/pkg/otel/receivers/verifierreceiver/.
• Per review feedback from @axw and @cmacknz, this receiver is EDOT Collector-only and belongs in elastic-agent under ELv2 rather than the shared Apache-licensed OTel components repo.
• Replaces Introduce verifier receiver to EDOT #12728 (which imported the receiver as an external dependency from opentelemetry-collector-components).

[mergify]

This pull request does not have a backport label. Could you fix it @jeniawhite? 🙏
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.

[swiatekm]

Let's move this to internal/edot, there's no reason for it to live in the elastic-agent module.

[cmacknz]

Also include a codeowners change marking your team as the owners of verifierreceiver

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

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

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

[elasticmachine]

Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane)

[cmacknz]

Only looked at the pieces outside of the verifier receiver itself, probably you want to assign an engineer from the cloud-services team to review that since they'll get all the following review requests for changes to it.

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

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

[cmacknz]

Structure looks good to me. I'll approve once you get approval from someone on your team that they want this to merge.

Alternatively, for a bit more work, you can take the structural parts of this to main with a stub for the verifier receiver and I'll approve that. Then this PR will request codeowner approval from the right people and you won't need someone from agent control plane to approve everytime you push.

[cmacknz]

Actually you'll probably need our approval because of go.mod changes, so don't bother with that. Just ping me/control plane once you have approval from your own team that this is good to merge and we'll approve.

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

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

[olegsu]

LGTM

The merge-base changed after approval.

The merge-base changed after approval.

[elasticmachine]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: dbd2dae

Failed CI Steps

• x86_64:non-sudo: default
• x86_64:non-sudo: default - platform-ingest-elastic-agent-debian-11-1772525581

History

• 💛 Build #36739 was flaky 22810f2
• 💛 Build #36701 was flaky f192dbc
• 💔 Build #36700 failed 94b9468
• 💔 Build #36699 failed 855516b
• 💔 Build #36611 failed 3a9dbf9
• 💔 Build #36610 failed 73b5fab

cc @jeniawhite