feat: quark receiver

[biscout42]

initial mock receiver

[mergify]

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

[github-actions]

TL;DR

golangci-lint failed on lint (macos-latest) because the new root go.work excludes the repository root module, so CI's golangci-lint run ./... starts from a directory outside the workspace module roots. Add the repo root to go.work or remove the workspace file if it is only for local experimentation.

Remediation

• Update go.work so the main Elastic Agent module is part of the workspace, for example add . to the use block alongside ./internal/edot and ./go-quark.
• If the in-tree go-quark copy is intended to satisfy github.com/elastic/go-quark, also align go-quark/go.mod's module path with that import path; otherwise the workspace entry for ./go-quark will not replace the dependency imported by the receiver.
• Re-run the lint workflow or locally run the same lint target after the workspace change to confirm golangci-lint run ./... can typecheck from the repository root.

Investigation details

Root Cause

The PR adds a root go.work containing only ./internal/edot and ./go-quark. With GOWORK pointing at that file, golangci-lint runs from the repository root with ./..., but the root directory is not one of the workspace module roots.

Evidence

• Workflow: https://github.com/elastic/elastic-agent/actions/runs/28663454948
• Job/step: lint (macos-latest) / golangci-lint
• Key log excerpt:

GOWORK='/Users/runner/work/elastic-agent/elastic-agent/go.work'
level=error msg="[linters_context] typechecking error: pattern ./...: directory /Users/runner/work/elastic-agent/elastic-agent is outside module roots (/Users/runner/work/elastic-agent/elastic-agent/internal/edot, /Users/runner/work/elastic-agent/elastic-agent/go-quark)"
##[error]golangci-lint exit with code 7

• Relevant PR changes:

go.work:
use (
    ./internal/edot
    ./go-quark
)

go-quark/go.mod:
module quark

Validation

• Not run locally; this report is based on the failed GitHub Actions job log and the PR file contents.

Follow-up

• The Windows and Ubuntu lint jobs were cancelled after the macOS lint failure, so they should be rechecked after the workspace fix.

---

What is this? | From workflow: PR Actions Detective

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

[infra-vault-gh-plugin-prod]

⏳ Build in-progress, with failures

• Buildkite Build
• Commit: b048bc0

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 2016
• Unit tests - fips140=only Windows 2022
• Unit tests - macOS 15 ARM
• Unit tests - macOS 15 ARM
• Unit tests - Windows 10
• Unit tests - Windows 11
• Unit tests - Windows 11 arm64
• Unit tests - fips140=only Windows 11 arm64
• 📦 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,zip (linux,windows)
• 📦 arm64: FIPS tar.gz,zip (linux,windows)
• 📦 amd64: Containers
• 📦 arm64: Containers
• 📦 amd64: FIPS Containers
• 📦 arm64: FIPS Containers

History

• 💔 Build #42426 failed 914b008
• 💔 Build #42425 failed ed66b38
• 💔 Build #42304 failed ca22a78
• 💔 Build #42302 failed ccabc86

cc @biscout42

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