[elastic-observability-automation]

What

elastic/beats@9.6 automatic sync

---

Bump beats

update-beats with 9.6

ran shell command ".ci/scripts/update-beats.sh '9.6'"

GitHub Action workflow link

---

Created automatically by Updatecli Options: Most of Updatecli configuration is done via its manifest(s). If you close this pull request, Updatecli will automatically reopen it, the next time it runs. If you close this pull request and delete the base branch, Updatecli will automatically recreate it, erasing all previous commits made. Feel free to report any issues at github.com/updatecli/updatecli. If you find this tool useful, do not hesitate to star our GitHub repository as a sign of appreciation, and/or to tell us directly on our chat!

[github-actions]

🤖 GitHub comments

Just comment with:

• run docs-build : Re-trigger the docs validation. (use unformatted text in the comment!)

[Copilot]

🔵 Needs a closer look

Dependency compatibility remains unverified and needs human review of standard and FIPS CI results.

No open issues 🎉

What changed in this PR

This automated sync updates APM Server’s Beats dependency from the 9.6 branch and refreshes related dependency metadata.

Changes:

• Updates Beats to commit f059ea8acf2a and Elastic Agent Client to v7.19.0.
• Refreshes module checksums and standard/FIPS license notices to match.

File	Description
NOTICE.txt	Updates dependency versions and license-file paths.
NOTICE-fips.txt	Applies matching updates to FIPS license notices.
go.sum	Updates checksums for both upgraded dependencies.
go.mod	Pins the new Beats and Elastic Agent Client versions.

_{Review effort: Balanced}

[Copilot]

🔵 Needs a closer look

Dependency metadata is consistent, but upstream compatibility with publishing, Fleet integration, and standard/FIPS builds remains unverified.

No open issues 🎉

_{Review effort: Balanced}

[Copilot]

🔵 Needs a closer look

Dependency metadata is consistent, but standard and FIPS build compatibility remains unverified and needs CI confirmation and human review.

No open issues 🎉

_{Review effort: Balanced}

[Copilot]

🟢 Approval recommended

No active review issues are reported for the dependency and license-notice updates.

No open issues 🎉

_{Review effort: Balanced}

[Copilot]

🟢 Approval recommended

No active review issues are reported for the Beats dependency update.

No open issues 🎉

_{Review effort: Balanced}

[Copilot]

🟢 Approval recommended

No active review issues are reported for the Beats dependency update and related dependency and license changes.

No open issues 🎉

_{Review effort: Balanced}

[Copilot]

🟢 Approval recommended

No active review issues are reported for the Beats dependency update and related dependency and license-notice changes.

No open issues 🎉

_{Review effort: Balanced}

[github-actions]

TL;DR

Buildkite failed before the PR command ran: the agent could not reach Elastic’s Docker registry/auth endpoints during repository pre-command setup. This looks like transient CI infrastructure/network failure, not a code regression from this PR.

Remediation

• Re-run the failed Buildkite job :package: DRA Prep (snapshot) / rebuild https://buildkite.com/elastic/apm-server-package/builds/13398.
• If it fails again, check connectivity/latency from Buildkite workers to docker.elastic.co and docker-auth.elastic.co, then retry once connectivity is restored.

Investigation details

Root Cause

Failure occurred in .buildkite/hooks/pre-command at the Docker login step (retry 4 docker login ...) before .buildkite/scripts/stage-dra-artifacts.sh executed. See .buildkite/hooks/pre-command:56-63.

This is classified as Infrastructure (external registry/auth timeout), not a code bug/test failure/dependency drift in the PR changes.

Evidence

• Build: https://buildkite.com/elastic/apm-server-package/builds/13398
• Job/step: :package: DRA Prep (snapshot)
• Key log excerpt (/tmp/gh-aw/buildkite-logs/apm-server-package-package-dra-prep-snapshot.txt):
  • Error response from daemon: Get "https://docker.elastic.co/v2/": ... Client.Timeout exceeded while awaiting headers
  • Get "https://docker-auth.elastic.co/auth?...": context deadline exceeded
  • Retry 4/4 exited 1, no more retries left.
  • Error: running "repository pre-command" shell hook: ... exited with status 1

Additional context:

• PR diff is dependency sync (NOTICE-fips.txt, NOTICE.txt, go.mod, go.sum), with no changes to Buildkite hooks/scripts.
• Checked for open flaky-test tracking issues in elastic/apm-server: none found.

Verification

• Local repro/tests: not run (failure is in CI pre-command infrastructure setup, prior to repository build/test command execution).

Follow-up

If repeat failures persist across retries, consider opening/triaging an infra incident for Buildkite egress to Elastic Docker registry/auth services.

---

What is this? | From workflow: Observability Agentic Workflow — Status

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

[Copilot]

🟢 Approval recommended

No active review issues are recorded for the Beats dependency update and related metadata changes.

No open issues 🎉

_{Review effort: Balanced}

[Copilot]

🟢 Approval recommended

No active review issues are reported for the dependency updates and refreshed license notices.

No open issues 🎉

_{Review effort: Balanced}

[mergify]

This pull request is now in conflicts. Could you fix it @elastic-observability-automation[bot]? 🙏
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 updatecli_9.6_updatecli-update-beats-9.6 upstream/updatecli_9.6_updatecli-update-beats-9.6
git merge upstream/9.6
git push upstream updatecli_9.6_updatecli-update-beats-9.6

[Copilot]

🔵 Needs a closer look

Missing upstream source changes and CI results leave compatibility of the updated core dependencies unverified, requiring maintainer validation of normal and requirefips builds and integration behavior.

No open issues 🎉

_{Review effort: Balanced}

[Copilot]

🟢 Approval recommended

No active review issues are identified for the Beats dependency update and related dependency metadata changes.

No open issues 🎉

_{Review effort: Balanced}

[infra-vault-gh-plugin-prod]

💚 Build Succeeded

• Buildkite Build
• Commit: 48ca17c

History

• 💚 Build #13518 succeeded 74c7c05
• 💚 Build #13474 succeeded 08764f9
• 💚 Build #13445 succeeded 2e13ba5
• 💔 Build #13398 failed 3a2c3cd
• 💚 Build #13358 succeeded dd71ade
• 💚 Build #13345 succeeded 7d2cb9c