8000 Releases · grafana/beyla · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Releases: grafana/beyla

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

v2.0.5

19 Feb 17:55
44b108e
Compare
Choose a tag to compare

What's Changed

Other changes/additions

Full Changelog: v2.0.4...v2.0.5

v2.0.4

12 Feb 19:31
ccc1a4b
Compare
Choose a tag to compare
8000

What's Changed

Other changes/additions

Full Changelog: v2.0.3...v2.0.4

v1.9.9

12 Feb 19:30
707adee
Compare
Choose a tag to compare

What's Changed

Other changes/additions

Full Changelog: v1.9.8...v1.9.9

v2.0.3

06 Feb 18:27
4efef91
Compare
Choose a tag to compare

What's Changed

Other changes/additions

  • Port 1596 to 2.0 by @grcevski in #1598
  • [release-2.0] Remove distributed traces limitation by @github-actions in #1616

Full Changelog: v2.0.2...v2.0.3

v2.0.2

29 Jan 23:49
0b47146
Compare
Choose a tag to compare

What's Changed

Other changes/additions

  • Fixed a bug affecting trace context propagation at library level for go services involving HTTP2 by @grcevski in #1590

Full Changelog: v2.0.1...v2.0.2

0