[updatecli][9.5] Update to elastic/beats

[elastic-observability-automation]

What

elastic/beats@9.5 automatic sync

---

Bump beats

update-beats with 9.5

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

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!)

[infra-vault-gh-plugin-prod]

💚 Build Succeeded

• Buildkite Build
• Commit: c008c79

[carsonip]

failing due to #21375

[mergify]

Merge Queue Status

• ✅ Entered queue — 2026-08-05 17:23 UTC · Rule: default · triggered by rule squash and merge updatecli PRs after CI passes
• ❌ Checks failed · on draft merge queue: checking 9.5 (e0537c1) and #21629 together #21632
• 🚫 Left the queue — 2026-08-06 17:52 UTC · at c008c79c118c2045f7130d5b4e683f7d2beab9a7

This pull request spent 1 day 29 minutes 15 seconds in the queue, including 50 minutes 31 seconds running CI.

Waiting for

• check-success=lint
• check-success=system-test
• check-success=test (macos-latest)
• any of:
  • check-success=test (windows-2025)
  • check-success=test (windows-latest)
• any of: [🛡 GitHub repository ruleset rule 9.*]
  • check-neutral = lint
  • check-skipped = lint
  • check-success = lint

All conditions

• check-success=lint
• check-success=system-test
• check-success=test (macos-latest)
• any of:
  • check-success=test (windows-2025)
  • check-success=test (windows-latest)
• any of [🛡 GitHub repository ruleset rule 9.*]:
  • check-neutral = lint
  • check-skipped = lint
  • check-success = lint
• check-success=CLA
• github-review-approved [🛡 GitHub repository ruleset rule 9.*]
  • [updatecli][9.5] Update to elastic/beats #21629
• github-review-approved [🛡 GitHub repository ruleset rule [org] Require a PR for Renovate]
  • [updatecli][9.5] Update to elastic/beats #21629
• github-review-approved [🛡 GitHub repository ruleset rule [org] Require a PR]
  • [updatecli][9.5] Update to elastic/beats #21629
• any of [🛡 GitHub repository ruleset rule 9.*]:
  • check-success = buildkite/docs-build-pr
  • check-neutral = buildkite/docs-build-pr
  • check-skipped = buildkite/docs-build-pr
• any of [🛡 GitHub repository ruleset rule 9.*]:
  • check-success = CLA
  • check-neutral = CLA
  • check-skipped = CLA

Reason

The merge conditions cannot be satisfied due to failing checks

• test (macos-latest)
• test (windows-2025)
• buildkite/docs-build-pr
• CLA

Failing checks:

• 🟠 lint (job log)
• 🟠 system-test (job log)
• 🛑 test (macos-latest) (job log)
• ❌ test (windows-2025) (job log)

Hint

You may have to fix your CI before adding the pull request to the queue again.
If you update this pull request, to fix the CI, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio queue comment.

Tick the box to put this pull request back in the merge queue (same as @mergifyio queue).

• Requeue this pull request