Skip to content

Releases: grafana/beyla

v2.4.2-pre-alloy

05 Jun 21:35
Compare
Choose a tag to compare
v2.4.2-pre-alloy Pre-release
Pre-release
Merge branch 'release-2.4-pre-alloy' of github.com:grafana/beyla into…

v2.2.4-alloy

22 May 23:13
Compare
Choose a tag to compare

Rebuild without gitlfs

v2.2.4

22 May 19:53
00eb8b7
Compare
Choose a tag to compare

What's Changed

Other changes/additions

Full Changelog: v2.2.3...v2.2.4

v2.2.3

15 May 14:47
Compare
Choose a tag to compare

What's Changed

Other changes/additions

Full Changelog: v2.2.2...v2.2.3

v2.2.2

12 May 15:46
aa506b1
Compare
Choose a tag to compare

What's Changed

Other changes/additions

Full Changelog: v2.2.1...v2.2.2

v2.2.1

08 May 04:25
1fb10f0
Compare
Choose a tag to compare

What's Changed

Other changes/additions

  • Remove PID to prevent cardinality explosion by @rafaelroquetto in #1908 - this fixes memory consumption issues

Full Changelog: v2.2.0...v2.2.1

v2.2.0

06 May 12:10
445eea9
Compare
Choose a tag to compare

What's Changed

Bug fixes 🐛

Other changes/additions

New Contributors

Full Changelog: v2.1.0...v2.2.0

v2.1.0

02 Apr 01:07
cd7746c
Compare
Choose a tag to compare

What's Changed

Breaking changes 🔨

  • Helm chart: do not override network flows attributes by @mariomac in #1632

Bug fixes 🐛

Other changes/additions

Read more

v2.0.7

19 Mar 22:46
385b212
Compare
Choose a tag to compare

What's Changed

Other changes/additions

This release features a backport of work done on the trace context propagation front to move the writing of traceparent headers from the TC level to the sock_msg level, ensuring trace context propagation does not disrupt applications such as istio.

Full Changelog: v2.0.6...v2.0.7

v2.0.6

17 Mar 14:12
575798d
Compare
Choose a tag to compare

What's Changed

Bug fixes 🐛

  • Allow defining extra resource labels in prometheus by @github-actions in #1744

Due to internal limitations of the Prometheus API client, Beyla needs to know beforehand which attributes are exposed
for each metric. This would cause that some attributes that are discovered at runtime, during instrumentation, won't
be visible by default. For example, attributes defined on each application via Kubernetes annotations, or in the
target application's OTEL_RESOURCE_ATTRIBUTES environment variable.

For example, an application defining the OTEL_RESOURCE_ATTRIBUTES=deployment.environment=production as environment
variable, the target_info{deployment.environment="production"} attribute would be visible by default if the metrics
are exported via OpenTelemetry but not if they are exported via Prometheus.

To make deployment_environment visible in Prometheus, you need to add it to the prometheus > extra_resource_attributes YAML property or BEYLA_PROMETHEUS_EXTRA_RESOURCE_ATTRIBUTES environment variable.

  • Fix OTEL HTTP exclusion detection by @github-actions in #1691

Other changes/additions

Full Changelog: v2.0.5...v2.0.6