[agent-suggestions] Agent suggestions - 2026-06-08

[github-actions]

Agent Suggestions

Date: 2026-06-08

1. trigger-backport-branch-health-guard

Trigger: workflow_run (on completed CI workflows) scoped to active backport branches, with optional pull_request_target hook when backport PRs are merged.

Purpose: Detect and deduplicate cases where a backport PR is merged while non-required checks fail (for example, failures hidden under allowed checks), leaving the target branch in a broken state and blocking subsequent backports.

Proposed safe outputs: create-issue (canonical branch-health tracker), add-comment (linking the tracker on the merged backport PR), noop (no actionable branch breakage).

Evidence:

• Open bug describing the exact gap: #51084 ([CI] Merged backported PRs with allowed failures can leave branches in a broken state).
• Concrete example cited in that issue: merged backport PR #51021 despite failing checks.
• Current backport automation only handles label-driven backport creation, not post-merge branch health triage: .github/workflows/backport-active.yml:3-7, .github/workflows/backport-active.yml:15-22.
• Existing detective workflows react to failing runs/statuses but are not branch-health-oriented for merged backports:
  • .github/workflows/trigger-pr-actions-detective.yml:3-5, .github/workflows/trigger-pr-actions-detective.yml:16-18
  • .github/workflows/trigger-pr-buildkite-detective.yml:3, .github/workflows/trigger-pr-buildkite-detective.yml:14-16

Why not covered already: Prior agent-suggestion issues currently open focus on other scopes (workflow-failure meta triage and downstream compatibility checks), not merged-backport branch-health guardrails.

Duplicate Checks

• Open issues reviewed: https://github.com/elastic/beats/issues?q=is:open+is:issue+repo:elastic%2Fbeats+%28agent+OR+workflow+OR+automation%29
• Open PRs reviewed: https://github.com/elastic/beats/pulls?q=is:open+is:pr+repo:elastic%2Fbeats+%28agent+OR+workflow%29
• Prior suggestion reports reviewed:
  • [agent-suggestions] Agent suggestions - 2026-04-20 #50211
  • [agent-suggestions] Agent suggestions - 2026-03-30 #49774
  • [aw] Agent Suggestions failed #50089

Downstream Signals

• Cross-repo AI-workflow adoption and CI-failure automation activity remains active, reinforcing value of targeted branch-health automation:
  • Enable AI Agentic Workflow for Buildkite build failure analysis logstash#19196
  • Add AI-driven Buildkite build failure analysis workflow package-registry#1745

Suggested Next Steps

• Prototype trigger-backport-branch-health-guard.yml with branch-level dedupe key (branch + check signature + merge SHA).
• Pilot on active maintenance branches first (for example, 8.19, 9.3, 9.4) and tune noise thresholds.
• Escalate to a single canonical issue per branch breakage pattern instead of per-run reporting.

Note

🔒 Integrity filter blocked 194 items

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

• [Flaky Test] x-pack.filebeat.tests.system.test_xpack_modules.XPackTest test_fileset_file_070_o365 #51146 list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• Enhancement: Make AWS billing metricset time range configurable #51135 list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• Fleet integration policy becomes uneditable when stale policy_id references a deleted agent policy despite valid policy_ids #51131 list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• osqreceiver integration test #51127 list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• packetbeat: process.* fields not populated for short-lived connections when monitor_processes is enabled #51125 list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• [Flaky Test] github.com/elastic/beats/v7/x-pack/filebeat/input/netflow TestNetFlowIntegration #51120 list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• Respect setup.pipelines.enabled for Beats ingest pipeline loading #51059 list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #50900 list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #51074 list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #51136 list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #51113 list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #51132 list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #50792 list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #51108 list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #50681 list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #51091 list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• ... and 178 more items

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: Agent Suggestions

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

• expires on Jun 15, 2026, 1:56 PM UTC

[botelastic]

This issue doesn't have a Team:<team> label.