Update to Beyla 2.7.10 by rafaelroquetto · Pull Request #5019 · grafana/alloy

rafaelroquetto · 2025-12-05T23:25:29Z

PR Description

Update Alloy to latest Beyla 2.7

Which issue(s) this PR fixes

BEGIN_COMMIT_OVERRIDE
fix: update beyla to 2.7.10
END_COMMIT_OVERRIDE

github-actions · 2025-12-05T23:27:26Z

🔍 Dependency Review

Below are the reviewed dependency updates detected in go.mod. Each section summarizes potential impact, links to upstream references, and any code changes you may need to consider.

Scope: Only dependencies changed in go.mod/go.sum are assessed. No assumptions are made beyond what can be inferred from versioning and publicly documented surfaces. Patch releases typically avoid breaking changes, but please verify against your code paths.

github.com/grafana/beyla/v2 v2.7.8 -> v2.7.10 — ⚠️ Needs Review

Reasoning:

Patch-level update (v2.7.x). By SemVer, breaking API changes are not expected; however, Beyla often evolves telemetry attributes and defaults that can affect downstream processing even without API breaks.
If your project imports Beyla packages (not just using the binary), any subtle behavior changes (e.g., configuration parsing, default detectors, attribute sets) can affect runtime behavior.

What to check:

Changelog between v2.7.8 and v2.7.10 for:
- Changes to exported telemetry attribute names/values (HTTP, gRPC, DB, messaging) that your code assumes in tests, processors, or dashboards.
- Any deprecations or changes in configuration structs in public packages (e.g., config types, option functions).
- Any changes in default settings (sampling, discovery, protocol detectors) that could alter produced telemetry volume or shape.

Suggested verification:

Compile and run unit tests focusing on:
- Code paths that parse or depend on Beyla-generated telemetry.
- Any usage of Beyla’s public config types and option functions.
Run a short integration test to validate emitted span/metric labels still match expectations.

Code changes likely required:

None identified at the API level for a patch bump. If you key on specific attribute names in your code, verify and adjust selectors accordingly.

Example selector resilience (if you rely on attribute strings; prefer semconv constants where possible):

- // Before (string literal usage risks breakage)
- if attrs["http.scheme"] == "https" { ... }

+ // After (use semconv constants to avoid drift)
+ scheme, _ := attrs[semconv.HTTPSchemeKey]
+ if string(scheme.AsString()) == "https" { ... }

References:

Releases/Changelog: https://github.com/grafana/beyla/releases (review 2.7.9 and 2.7.10)

replace go.opentelemetry.io/obi => github.com/grafana/opentelemetry-ebpf-instrumentation v1.3.10 -> v1.3.13 — ⚠️ Needs Review

Reasoning:

This is a replace update affecting all imports of go.opentelemetry.io/obi. Even as a patch update, eBPF instrumentation layers can tweak event schemas or defaults.
If your code imports go.opentelemetry.io/obi packages (types, event models, loaders/options), confirm no API drift or behavior changes.

What to check:

Changelog between v1.3.10 and v1.3.13 for:
- Struct field additions/renames in any exported event or config types you use.
- Option function changes (e.g., WithXxx/EnableXxx) and their defaults.
- Telemetry attribute or semantic conventions alignment changes (e.g., HTTP/gRPC attributes).

Suggested verification:

Rebuild and run tests for any code handling OBI events.
Validate span/metric attribute expectations in tests (especially if you assert on attribute presence/values).

Code changes likely required:

None typically for a patch release; make defensive reads of optional/added fields if you unmarshal events.

Example defensive parsing (if consuming JSON events from OBI):

- type HTTPEvent struct {
-   Method string `json:"method"`
-   // ...
- }

+ type HTTPEvent struct {
+   Method string  `json:"method"`
+   // Tolerate newly added fields without failing strict decoders
+   // json.Decoder with DisallowUnknownFields() should be avoided or gated:
+ }

References:

Releases/Changelog: https://github.com/grafana/opentelemetry-ebpf-instrumentation/releases (review 1.3.11–1.3.13)

Notes

No new direct dependencies were introduced; only version bumps and a replace update were changed.
Because both updates are patch-level, compile-time API breaks are unlikely, but behavior-level changes (telemetry attributes, defaults) can still affect your downstream processing. Run integration tests that validate emitted telemetry shape.

(cherry picked from commit 615bb61)

fix: update to Beyla 2.7.10 (#5019) (cherry picked from commit 615bb61) Co-authored-by: Rafael Roquetto <rafaelroquetto@users.noreply.github.com>

This MR contains the following updates: | Package | Update | Change | |---|---|---| | [grafana/alloy](https://github.com/grafana/alloy) | patch | `v1.12.0` -> `v1.12.1` | MR created with the help of [el-capitano/tools/renovate-bot](https://gitlab.com/el-capitano/tools/renovate-bot). **Proposed changes to behavior should be submitted there as MRs.** --- ### Release Notes <details> <summary>grafana/alloy (grafana/alloy)</summary> ### [`v1.12.1`](https://github.com/grafana/alloy/releases/tag/v1.12.1) [Compare Source](grafana/alloy@v1.12.0...v1.12.1) ##### Bug Fixes 🐛 - update to Beyla 2.7.10 ([#5019](grafana/alloy#5019)) ([c149393](grafana/alloy@c149393)) ([@rafaelroquetto](https://github.com/rafaelroquetto)) #### Upgrading Read the [release notes] for specific instructions on upgrading from older versions: [release notes]: https://grafana.com/docs/alloy/v1.12/release-notes/ #### Installation Refer to our [installation guide] for how to install Grafana Alloy. [installation guide]: https://grafana.com/docs/alloy/v1.12/get-started/install/ </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Enabled. ♻ **Rebasing**: Whenever MR is behind base branch, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this MR and you won't be reminded about this update again. --- - [ ] If you want to rebase/retry this MR, check this box --- This MR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate).

This PR contains the following updates: | Package | Update | Change | |---|---|---| | [docker.io/grafana/alloy](https://github.com/grafana/alloy) | patch | `v1.12.0` -> `v1.12.1` | --- > ⚠️ **Warning** > > Some dependencies could not be looked up. Check the Dependency Dashboard for more information. --- ### Release Notes <details> <summary>grafana/alloy (docker.io/grafana/alloy)</summary> ### [`v1.12.1`](https://github.com/grafana/alloy/releases/tag/v1.12.1) [Compare Source](grafana/alloy@v1.12.0...v1.12.1) ##### Bug Fixes 🐛 - update to Beyla 2.7.10 ([#5019](grafana/alloy#5019)) ([c149393](grafana/alloy@c149393)) ([@rafaelroquetto](https://github.com/rafaelroquetto)) #### Upgrading Read the [release notes] for specific instructions on upgrading from older versions: [release notes]: https://grafana.com/docs/alloy/v1.12/release-notes/ #### Installation Refer to our [installation guide] for how to install Grafana Alloy. [installation guide]: https://grafana.com/docs/alloy/v1.12/get-started/install/ </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate).  Co-authored-by: Renovate Bot <renovate@zarantonello.dev> Co-committed-by: Renovate Bot <renovate@zarantonello.dev>

Update to Beyla 2.7.10

d3bb4d9

rafaelroquetto requested a review from a team as a code owner December 5, 2025 23:25

rafaelroquetto requested review from grcevski and ptodev and removed request for a team December 5, 2025 23:25

kalleep approved these changes Dec 8, 2025

View reviewed changes

rafaelroquetto merged commit 615bb61 into main Dec 8, 2025
43 checks passed

rafaelroquetto deleted the rafael/beyla-2.7.10 branch December 8, 2025 16:06

dehaansa pushed a commit to madhub/alloy that referenced this pull request Dec 10, 2025

Update to Beyla 2.7.10 (grafana#5019)

0e8b1e6

jharvey10 added backport/v1.12 Backport to release/v1.12 and removed backport/v1.12 Backport to release/v1.12 labels Dec 12, 2025

jharvey10 pushed a commit that referenced this pull request Dec 12, 2025

fix: update to Beyla 2.7.10 (#5019)

fd820e3

(cherry picked from commit 615bb61)

jharvey10 mentioned this pull request Dec 12, 2025

chore: backport #5019 #5082

Merged

jharvey10 added a commit that referenced this pull request Dec 12, 2025

chore: backport #5019 (#5082)

c149393

fix: update to Beyla 2.7.10 (#5019) (cherry picked from commit 615bb61) Co-authored-by: Rafael Roquetto <rafaelroquetto@users.noreply.github.com>

This was referenced Dec 12, 2025

chore(release/v1.12): release 1.12.1 #5083

Closed

chore(release/v1.12): release 1.12.1 #5085

Closed

chore(release/v1.12): release 1.12.1 #5086

Closed

chore(release/v1.12): release 1.12.1 #5091

Closed

chore(release/v1.12): release 1.12.1 #5106

Merged

BrewTestBot mentioned this pull request Dec 15, 2025

grafana-alloy 1.12.1 Homebrew/homebrew-core#258779

Merged

github-actions bot added the frozen-due-to-age label Dec 27, 2025

github-actions bot locked as resolved and limited conversation to collaborators Dec 27, 2025

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Update to Beyla 2.7.10#5019

Update to Beyla 2.7.10#5019
rafaelroquetto merged 1 commit intomainfrom
rafael/beyla-2.7.10

rafaelroquetto commented Dec 5, 2025 •

edited by jharvey10

Loading

Uh oh!

github-actions bot commented Dec 5, 2025

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Conversation

rafaelroquetto commented Dec 5, 2025 • edited by jharvey10 Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

PR Description

Which issue(s) this PR fixes

Uh oh!

github-actions bot commented Dec 5, 2025

🔍 Dependency Review

Notes

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

rafaelroquetto commented Dec 5, 2025 •

edited by jharvey10

Loading