[agent-suggestions] Agent suggestions - 2026-07-27

## Agent Suggestions
**Date:** 2026-07-27

### 1. `trigger-pr-binary-size-impact-reporter`
**Trigger:** `pull_request` events for `opened`, `synchronize`, `reopened`, and `ready_for_review`, with path-aware filtering for Go source, dependencies, build configuration, `libbeat`, and Beat source changes; skip docs-only changes.

**Purpose:** Build the affected Beat binaries for the PR base and head with identical toolchain and flags, compare their on-disk sizes, and publish a concise per-binary delta table. Highlight meaningful regressions and include links to the produced artifacts so maintainers can catch resource-footprint growth before merge. This directly supports Beats’ lightweight footprint promise and should be read-only and idempotent.

**Proposed safe outputs:** `add-comment` on the PR with base/head sizes, absolute and percentage deltas, threshold warnings, and artifact links; `noop` when no report is needed. No code changes, labels, or issues.

**Evidence:**
- [Issue #52212](https://github.com/elastic/beats/issues/52212) explicitly states that Beats has no binary-size tracking and requests automated measurement on every PR.
- A maintainer comment on [#52212](https://github.com/elastic/beats/issues/52212#issuecomment-5050414895) says the improvement is particularly needed for Elastic Agent because of disk-size reduction needs, establishing downstream impact.
- The repository defines “lightweight” as having a small installation footprint and using limited system resources in [`README.md:12-13`](https://github.com/elastic/beats/blob/main/README.md#L12-L13).
- [`trigger-performance-profiler.yml:1-23`](https://github.com/elastic/beats/blob/main/.github/workflows/trigger-performance-profiler.yml#L1-L23) runs on a weekday schedule and delegates performance profiling; it does not measure or report PR binary-size deltas.
- [`trigger-pr-review.yml:1-25`](https://github.com/elastic/beats/blob/main/.github/workflows/trigger-pr-review.yml#L1-L25) provides generic PR review and has no artifact-size measurement or comparison step.

**Why not covered already:** Existing agent workflows cover generic PR review and scheduled runtime performance profiling, but neither performs reproducible base-versus-head binary-size measurement on the PR. The requested workflow is a narrow artifact-footprint guardrail that operationalizes the open #52212 task without duplicating code review or profiling.

## Duplicate Checks
- Reviewed prior open agent-suggestion reports [#52087](https://github.com/elastic/beats/issues/52087), [#51891](https://github.com/elastic/beats/issues/51891), [#51744](https://github.com/elastic/beats/issues/51744), [#51416](https://github.com/elastic/beats/issues/51416), [#51149](https://github.com/elastic/beats/issues/51149), [#50211](https://github.com/elastic/beats/issues/50211), and [#49774](https://github.com/elastic/beats/issues/49774); none proposes binary-size reporting.
- The existing local workflow inventory includes generic PR review and performance profiling, but no binary-size workflow.

## Downstream Signals
- [#52212 comment](https://github.com/elastic/beats/issues/52212#issuecomment-5050414895) identifies Elastic Agent as the downstream consumer most in need of disk-size reduction.
- The root repository documentation defines the product as lightweight, so regressions affect both Beats distributions and downstream packaging consumers.

## Suggested Next Steps
- [ ] Define canonical build flags and a stable artifact naming scheme for each supported Beat and platform.
- [ ] Set initial warning thresholds for absolute and percentage growth, and suppress duplicate comments for unchanged PR head SHAs.
- [ ] Coordinate the measurement format with Elastic Agent so the same report can be consumed by downstream packaging checks.

---
[What is this?](https://ela.st/github-ai-tools) | [From workflow: Agent Suggestions](https://github.com/elastic/beats/actions/runs/30269199458)

Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.
> - [x] expires on Aug 3, 2026, 1:21 PM UTC

Start by reading .github/workflows/trigger-performance-profiler.yml and .github/workflows/trigger-pr-review.yml, then review issue #52212 for the requested binary-size tracking context. Define the supported Beat builds, flags, artifact naming, thresholds, and duplicate-comment behavior before implementing the PR workflow. Done means reproducible base-versus-head size reports with artifact links and no-op behavior when reporting is unnecessary.

Written by the indexing model from the issue text.