[updatecli] Update to elastic/beats@58f44bb27b80

[elastic-observability-automation]

What

elastic/beats automatic sync

Changeset

• elastic/beats@58f44bb27b80

---

Bump beats

Update to elastic/beats@58f44bb27b80

ran shell command ".ci/scripts/update-beats.sh 58f44bb27b80"

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

Expand to view the GitHub comments

Just comment with:

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

[kruskall]

@Mergifyio queue

[mergify]

queue

🟠 Waiting for conditions to match

• any of: [🔀 queue conditions]
  • all of: [📌 queue conditions of queue default]
    • branch-protection-review-decision = APPROVED [🛡 GitHub branch protection]
    • #approved-reviews-by >= 1 [🛡 GitHub branch protection]
    • #approved-reviews-by >= 1 [🛡 GitHub repository ruleset rule]
    • #approved-reviews-by >= 1 [🛡 GitHub repository ruleset rule]
    • #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
    • #changes-requested-reviews-by = 0 [🛡 GitHub repository ruleset rule]
    • #changes-requested-reviews-by = 0 [🛡 GitHub repository ruleset rule]
    • any of: [🛡 GitHub branch protection]
      • check-success = lint
      • check-neutral = lint
      • check-skipped = lint
    • any of: [🛡 GitHub branch protection]
      • check-success = system-test
      • check-neutral = system-test
      • check-skipped = system-test
    • any of: [🛡 GitHub branch protection]
      • check-success = CLA
      • check-neutral = CLA
      • check-skipped = CLA
    • any of: [🛡 GitHub branch protection]
      • check-success = docs-preview / build
      • check-neutral = docs-preview / build
      • check-skipped = docs-preview / build
• -closed [📌 queue requirement]
• -conflict [📌 queue requirement]
• -draft [📌 queue requirement]
• any of: [📌 queue -> configuration change requirements]
  • -mergify-configuration-changed
  • check-success = Configuration changed

[kruskall]

@Mergifyio update

[mergify]

update

✅ Branch has been successfully updated

[kruskall]

@Mergifyio queue

[mergify]

queue

🛑 The pull request could not be merged

This could be related to an activated branch protection or ruleset rule that prevents us from merging. (details: 4 of 4 required status checks are expected.)

[mergify]

This pull request has been removed from the queue for the following reason: pull request dequeued.

Pull request #17660 has been dequeued. The pull request could not be merged. This could be related to an activated branch protection or ruleset rule that prevents us from merging. (details: 4 of 4 required status checks are expected.).

You can check the last failing draft PR here: #17702.

You should look at the reason for the failure and decide if the pull request needs to be fixed or if you want to requeue it.
If you do update this pull request, 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 requeue comment.

[mergify]

This pull request has been removed from the queue for the following reason: pull request dequeued.

Pull request #17660 has been dequeued. The pull request rule doesn't match anymore.

You can check the last failing draft PR here: #17705.

You should look at the reason for the failure and decide if the pull request needs to be fixed or if you want to requeue it.
If you do update this pull request, 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 requeue comment.