Update grafana/beyla Docker tag to v1.9.7 #972
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
renovate
bot
added
dependency/docker
renovate
bot
force-pushed
the
renovate/grafana-beyla-1.x
branch
from
744d12e to
872981b
Compare
renovate
bot
changed the title
Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
renovate
bot
force-pushed
the
renovate/grafana-beyla-1.x
branch
from
872981b to
9e0d2df
Compare
renovate
bot
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
1.8.0->1.9.7Release Notes
grafana/beyla (grafana/beyla)
v1.9.7Compare Source
What's Changed
Bug fixes 🐛
In Beyla 1.6, we introduced a regression that kept Beyla running if one of their subcomponents failed, causing that the lack of instrumentation might remain unnoticed.
Full Changelog: grafana/beyla@v1.9.6...v1.9.7
v1.9.6Compare Source
What's Changed
Other changes/additions
Full Changelog: grafana/beyla@v1.9.5...v1.9.6
v1.9.5Compare Source
What's Changed
Other changes/additions
Full Changelog: grafana/beyla@v1.9.4...v1.9.5
v1.9.4Compare Source
What's Changed
Other changes/additions
Full Changelog: grafana/beyla@v1.9.3...v1.9.4
v1.9.3Compare Source
What's Changed
Adds the
BEYLA_KUBE_META_RESTRICT_LOCAL_NODEconfiguration option that allows configuring the local informer to only watch the Kubernetes Pods from the local node. This will alleviate the memory load, especially during startup.Other changes/additions
Full Changelog: grafana/beyla@v1.9.2...v1.9.3
v1.9.2Compare Source
What's Changed
Other changes/additions
Full Changelog: grafana/beyla@v1.9.1...v1.9.2
v1.9.1Compare Source
What's Changed
Other changes/additions
Full Changelog: grafana/beyla@v1.9.0...v1.9.1
v1.9.0Compare Source
What's Changed
Beyla 1.9.0 is released with major internal changes, in preparation to what's coming for the future Beyla 2.0 release.
Breaking changes 🔨
Removed
override_instance_idconfiguration optionThis option was aimed uniquely for debugging purposes.
More info: https://github.com/grafana/beyla/pull/1125
Fix instance and job in Prometheus exporter
Renaming
target_instancePrometheus attribute toinstance. Also, thejobattribute has been added to Prometheus.Now, all the metrics are consistent, no matter they are exported via OTEL or Prometheus.
More info: https://github.com/grafana/beyla/pull/1130
Set OTEL service name and namespace from application environment variables
If the application has set the
OTEL_SERVICE_NAMEorOTEL_SERVICE_NAMESPACEvariables in its environment,Beyla will use them to set the reported service name and namespace.
If the variables are not there, Beyla will use the previously existing mechanism to set service name and namespace.
Bug fixes 🐞
Fix cgroup ID parsing in newest Docker versions
More info: https://github.com/grafana/beyla/pull/1287
Fix OS capability checking
There were few bugs in the OS capability checking which are being fixed with this PR:
More info: https://github.com/grafana/beyla/pull/1131
What's new
Introduce option for high volume request tracking
Beyla tracks the full request completion time, this typically means we look to see if the application is responding
with more data after the first HTTP response. One example would be a large file download, where the majority of the time
is actually serializing the data on the wire. When the client uses keep-alive, we don't necessarily see the connection
close event, but we tell by new pushed requests that we should terminate an earlier request.
This approach doesn't work well in when there's high volume of requests, e.g. beyond our current map sizing. The delayed
requests will likely be booted out of the map before we have a chance to complete them.
The
BEYLA_BPF_HIGH_REQUEST_VOLUMEconfiguration option forces Beyla to complete the request as soon as the responseis finished. It will produce less accurate accounting for large file downloads, but it will avoid no data for high
volume of requests.
More info: https://github.com/grafana/beyla/pull/1192
Use
scratchas the base to build the Beyla docker imagesIt provides smaller images, as well as removing the risk for any potential vulnerability in the base image.
More info: https://github.com/grafana/beyla/pull/1367
Kubernetes: no need for a privileged init container anymore
The way Beyla internally mounts and shares some eBPF data structures has changed. This removes the necessity of
giving Beyla elevated privileges, or creating a privileged init container to mount the BPF file system.
More info: https://github.com/grafana/beyla/pull/1251
Experimental: Kubernetes API cache service
To decorate the traces and metrics with Kubernetes metadata, each Beyla instance establishes a connection to the
Kubernetes cache service. On big clusters (500+ nodes, 500+ Beyla instances), this action could greatly overload the
Kubernetes API because listening for cluster-global resources is really expensive.
Experimentally, you can configure Beyla to move the Kube API subscription logic to an external service (with fewer
instances), and connect Beyla to the Kubernetes API cache service instead of the Kubernetes API directly.
The easiest way to enable this service is via our latest Helm chart, in
values.yml:Other changes/additions
New Contributors
Full Changelog: grafana/beyla@v1.8.8...v1.9.0
v1.8.9Compare Source
What's Changed
Other changes/additions
Full Changelog: grafana/beyla@v1.8.8...v1.8.9
v1.8.8Compare Source
What's Changed
Other changes/additions
Full Changelog: grafana/beyla@v1.8.7...v1.8.8
v1.8.6Compare Source
What's Changed
Other changes/additions
Full Changelog: grafana/beyla@v1.8.5...v1.8.6
v1.8.5Compare Source
What's Changed
Other changes/additions
Full Changelog: grafana/beyla@v1.8.4...v1.8.5
v1.8.4Compare Source
What's Changed
Other changes/additions
Full Changelog: grafana/beyla@v1.8.3...v1.8.4
v1.8.3Compare Source
What's Changed
Bug fixes 🐛
Other changes/additions
Full Changelog: grafana/beyla@v1.8.1...v1.8.3
v1.8.1Compare Source
What's Changed
Update OTEL collector library from v0.102.0 to v0.108.1. This should have no visible effect on users but will enable the integration of Beyla in the next version of Grafana Alloy.
Full Changelog: grafana/beyla@v1.8.0...v1.8.1
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.
This PR was generated by Mend Renovate. View the repository job log.