EDOT collector: include akamaisiemreceiver

[ShourieG]

Type of change

• Enhancement

What does this PR do?

Register the akamaisiemreceiver in the EDOT collector's default component
factory so the agent accepts policies that reference the akamai_siem receiver
type.

Proposed Commit Message

edot/otelcol: register akamaisiemreceiver in component factory

Register the akamaisiemreceiver in the EDOT collector's default component
factory so the agent accepts policies that reference the akamai_siem receiver
type.

The receiver has no FIPS or OS restriction so it belongs in default.go
alongside the other platform-independent receivers.

Why is it important?

Without this, any Fleet policy using the native OTel Akamai SIEM input would
be rejected at startup because the collector has no factory registered for
that component type.

Checklist

• [ x] 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

Disruptive User Impact

None

How to test this PR locally

Related issues

• Closes https://github.com/elastic/security-integrations/issues/764
• Relates [receiver/akamaisiemreceiver] - Initial implementation of Akamai SIEM native OTEL receiver opentelemetry-collector-components#1119

Questions to ask yourself

• How are we going to support this in production?
• How are we going to measure its adoption?
• How are we going to debug this?
• What are the metrics I should take care of?
• ...

[mergify]

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

[cmacknz]

Please add this to the all-components.yml configuration to make sure the collector will start when this component is present:

elastic-agent/internal/pkg/otel/testdata/all-components.yml

Line 58 in 1d37cd4

receivers:

[elasticmachine]

💔 Build Failed

• Buildkite Build
• Commit: 0f05396

Failed CI Steps

• check-ci
• Unit tests - Ubuntu 22.04
• Unit tests - Ubuntu 22.04
• Unit tests - Ubuntu 22.04 with requirefips build tag
• Unit tests - Ubuntu 22.04 with requirefips build tag
• Unit tests - fips140=only Ubuntu 22.04
• Unit tests - fips140=only Ubuntu 22.04
• Unit tests - Ubuntu 22.04 ARM64
• Unit tests - Ubuntu 22.04 ARM64
• Unit tests - Windows 2022
• Unit tests - Windows 2022
• Unit tests - Windows 2016
• Unit tests - Windows 2016
• Unit tests - macOS 15 ARM
• Unit tests - macOS 15 ARM
• Unit tests - Windows 10
• Unit tests - Windows 10
• Unit tests - Windows 11
• Unit tests - Windows 11
• Unit tests - Windows 11 arm64
• Unit tests - Windows 11 arm64
• :junit: Junit annotate
• 📦 amd64: zip,tar.gz,rpm,deb
• 📦 amd64: zip,tar.gz,rpm,deb
• 📦 amd64: FIPS tar.gz,zip (linux,windows)
• 📦 amd64: FIPS tar.gz,zip (linux,windows)
• 📦 arm64: zip,tar.gz
• 📦 arm64: zip,tar.gz
• 📦 arm64: FIPS tar.gz
• 📦 arm64: FIPS tar.gz
• 📦 amd64: Containers
• 📦 arm64: Containers
• 📦 amd64: FIPS Containers
• 📦 arm64: FIPS Containers
• Aggregate test reports
• ESS FIPS stack cleanup
• Aggregate test reports
• Trigger Serverless Beats Tests
• :pipeline: Run elastic-agent-package with agent core built locally
• DRY RUN publish to serverless

History

• 💔 Build #39437 failed ade46bb
• 💔 Build #39406 failed 9877775
• 💔 Build #39392 failed 2149564
• 💔 Build #39371 failed d283e35

cc @ShourieG

[github-actions]

TL;DR

Buildkite is failing at magefile compilation before tests/package steps run, due to a missing root-module checksum entry for github.com/elastic/go-concert/unison. This is a dependency issue (not a test flake): update root go.mod/go.sum to include the dependency version required by the current beats import graph.

Remediation

• In the PR branch, refresh root module deps (for example mage tidy or go get github.com/elastic/beats/v7/libbeat/statestore@v7.0.0-alpha2.0.20260507213829-7bbe8ee6dcfb) and commit resulting root go.mod/go.sum updates.
• Ensure root module resolves github.com/elastic/go-concert at the version that provides unison (current root files show v0.3.0 in go.mod/go.sum, while logs request a newer beats graph).
• Re-run check-ci and one unit-test job to confirm magefiles compile successfully.

Investigation details

Root Cause

The earliest failing point across jobs is dependency resolution while compiling magefiles:

• /tmp/gh-aw/buildkite-logs/elastic-agent-check-ci.txt:127
• /tmp/gh-aw/buildkite-logs/elastic-agent-unit-tests---ubuntu-2204.txt:129
• /tmp/gh-aw/buildkite-logs/elastic-agent-package-amd64-ziptargzrpmdeb.txt:135

All show the same error:

beats/libbeat/statestore/store.go:25:2: missing go.sum entry for module providing package github.com/elastic/go-concert/unison (imported by github.com/elastic/beats/v7/libbeat/statestore)

This cascades into downstream step failures (junit annotate, aggregate test reports, package jobs) because no test/package artifacts are produced.

Relevant repo state in this checkout (root module):

• go.mod:190 → github.com/elastic/go-concert v0.3.0 // indirect
• go.sum:255-256 → only github.com/elastic/go-concert v0.3.0 checksums

Evidence

• Build: https://buildkite.com/elastic/elastic-agent/builds/39489
• First failing step: check-ci (.buildkite/scripts/steps/check-ci.sh)
• Representative excerpt:

beats/libbeat/statestore/store.go:25:2: missing go.sum entry for module providing package github.com/elastic/go-concert/unison ...
Error: error compiling magefiles

Verification

Not run locally (this runner does not have mage installed), but logs are consistent across Linux/macOS/Windows unit and packaging jobs.

Follow-up

I could not read prior PR comments via GitHub MCP due integrity restrictions in this run, so I could not conclusively deduplicate against previous detective comments.

Note

🔒 Integrity filter blocked 2 items

The following items were blocked because they don't meet the GitHub integrity level.

• EDOT collector: include akamaisiemreceiver #14263 pull_request_read: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #14263 pull_request_read: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".

To allow these resources, lower min-integrity in your GitHub frontmatter:

tools:
  github:
    min-integrity: approved  # merged | approved | unapproved | none

---

What is this? | From workflow: PR Buildkite Detective

Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.

[ShourieG]

@cmacknz, made the recommended changes, tests are all passing now

[infra-vault-gh-plugin-prod]

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