NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Go modules, #948 by repository stars
Latest stable
v1.9.9
Last release 2 years ago
no release in 18 months
Ships on a steady schedule
a new release about every 9 days
Nearly every release is documented
notes for 53 of 55 stable releases
Nothing withdrawn
no release was ever pulled
3 years old
278 releases · first in 2023
Drag across the ruler to compare, or tap a release to open it.
Nothing published for this version
Nothing published for this version
Nothing published for this version
> ⚠️ Network metrics is an experimental under development feature, expect breaking changes in the short term.
Your coding agent can read these notes before it upgrades. Set up the MCP server →
⚠️ Network metrics is an experimental under development feature, expect breaking changes in the short term.
In addition to application-level metrics, Beyla can provide now the beyla.network.flow.bytes network-level metric, which captures the network bytes between two endpoints in a host.
This feature is independent from the Beyla application observability feature, and is application-agnostic. Beyla will capture all the network metrics in the host, independently of which applications is Beyla instrumenting.
To learn how to activate and configure network metrics, refer to the Grafana Beyla network documentation
Full Changelog: https://github.com/grafana/beyla/compare/v1.3.3...v1.4.0
<!-- Release notes generated using configuration in .github/release.yml at release-1.3 -->
<!-- Release notes generated using configuration in .github/release.yml at release-1.3 -->
Full Changelog: https://github.com/grafana/beyla/compare/v1.3.3...v1.3.4
<!-- Release notes generated using configuration in .github/release.yml at release-1.3 -->
<!-- Release notes generated using configuration in .github/release.yml at release-1.3 -->
Full Changelog: https://github.com/grafana/beyla/compare/v1.3.2...v1.3.3
<!-- Release notes generated using configuration in .github/release.yml at release-1.3 -->
<!-- Release notes generated using configuration in .github/release.yml at release-1.3 -->
Full Changelog: https://github.com/grafana/beyla/compare/v1.3.1...v1.3.2
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
We have updated the metrics collection names to the stable HTTP spec for OpenTelemetry. This change also applies to our Prometheus metrics exporter: h
We have updated the metrics collection names to the stable HTTP spec for OpenTelemetry. This change also applies to our Prometheus metrics exporter: https://github.com/open-telemetry/semantic-conventions/blob/main/docs/http/http-metrics.md
Users should update their dashboards, alerts, etc, from the following old to the following new names.
Old Prometheus metric names:
http_server_duration_secondshttp_client_duration_secondshttp_server_request_size_byteshttp_client_request_size_bytesOld OTEL metric names:
http.server.durationhttp.client.durationhttp.server.request.sizehttp.client.request.sizeNew Prometheus metric names:
http_server_request_duration_secondshttp_client_request_duration_secondshttp_server_request_body_size_byteshttp_client_request_body_size_bytesNew OTEL metric names:
http.server.request.durationhttp.client.request.durationhttp.server.request.body.sizehttp.client.request.body.sizeThe way GKE internally stored the container IDs in the /proc filesystem was not recognized by Beyla. In consequence, Beyla was not able to match process/container low-level information with high-level Kubernetes metadata.
This could also happen with other Kubernetes distributions.
For Prometheus, native histograms are enabled if you
enable the native-histograms feature in your Prometheus collector.
For OpenTelemetry you can use exponential histograms for the predefined histograms instead of defining the buckets manually. You need to set up the standard OTEL_EXPORTER_OTLP_METRICS_DEFAULT_HISTOGRAM_AGGREGATION environment variable. See the Beyla documentation for more information.
Under some high-load scenarios (a single Beyla instance instrumenting 80 containers), the virtual memory space was in the order of GigaBytes.
In the test results, the virtual memory (container_memory_usage_bytes and container_memory_working_set_bytes) decreased from 155MiB to 84MiB on 1 container instrumentation, and 3.5GiB to 338MiB when load tested with about 80 containers.
RSS (container_memory_rss) didn't change much. About 75MiB with 1 container and 206MiB when load tested.
publish-technical-documentation-release workflow for tag events by @jdbaldry in https://github.com/grafana/beyla/pull/583Full Changelog: https://github.com/grafana/beyla/compare/v1.2.1...v1.3.1
Nothing published for this version
We have improved the integration of Beyla with Kubernetes DaemonSets, ReplicaSets and StatefulSets.
We have improved the integration of Beyla with Kubernetes DaemonSets, ReplicaSets and StatefulSets.
Kubernetes discovery mechanism now accepts the following arguments:
k8s_statefulset_namek8s_daemonset_nameAlso, the metrics and traces can be decorated with the following metadata when it applies:
k8s.replicaset.namek8s.statefulset.namek8s.daemonset.nameDue to internal limitations in the way we use the Prometheus SDK (aiming for performance), metrics exported by our Prometheus exporter node will be decorated with all the k8s_statefulset_name, k8s_daemonset_name, k8s_deployment_name, and k8s_replicaset_name arguments, having empty values where it does not apply.
The above does not apply for OpenTelemetry-exported metrics that are later converted to Prometheus (e.g. in Grafana Cloud, Grafana Agent or an Opentelemetry Collector).
Full Changelog: https://github.com/grafana/beyla/compare/v1.2.0...v1.2.1
⚠️ this might lead to a breaking change in some Docker compose setups.
command arguments⚠️ this might lead to a breaking change in some Docker compose setups.
In the Beyla Dockerfile, we replaced CMD by ENTRYPOINT in Beyla, as it should be the standard way of specifying a container command.
This will cause that some docker-compose setups will break because this command value won't be valid anymore:
command:
- /beyla
- --config=config-file.yml
The correct and standard way will be:
command:
- --config=config-file.yml
Kubernetes deployments will still keep working because they accept either command for the whole CLI and args for the arguments.
In addition, the BEYLA_CONFIG_PATH environment variable is now the preferred way to specify the configuration file path in Docker and Kubernetes environments.
Beyla 1.0, was able to read the Traceparent header of the incoming service calls and report it as part of the generated traces. However, it was not able to inject the traceparent header in the outgoing calls of the instrumented service.
This means that it was possible to relate a service span with its parent trace, but not with their child invocations to other services, as the trace parent was lost.
For Go services Beyla 1.2 is able to inject the traceparent header to the child service requests from an instrumented application, enabling fully distributed traces.
For more information, read the distributed traces documentation.
In Beyla 1.0, the user could select which applications to instrument by specifying their used ports or the name of the executable file. These criteria were difficult to use to select Kubernetes Pods or Services, as they work in a higher level of abstraction.
Beyla 1.2 allows specifying the following service selection criteria: k8s_namespace, k8s_deployment_name, k8s_replicaset_name and/or k8s_pod_name.
You need to run Beyla with the BEYLA_KUBE_METADATA_ENABLE configuration option set to true.
For more information, read the Kubernetes tutorial.
Beyla 1.0 allowed, as an experimental-hidden (undocumented) feature, decorating metrics and traces with Kubernetes metadata about source and destination Pods. These attributes were not standard and, due to an experimental implementation, not 100% reliable.
Beyla 1.2 can decorate any metric with the following, standard OpenTelemetry attributes:
k8s.namespace.namek8s.deployment.namek8s.node.namek8s.pod.namek8s.pod.uidk8s.pod.start_timeYou need to run Beyla with the BEYLA_KUBE_METADATA_ENABLE configuration option
set to true.
For more information, read the Kubernetes tutorial.
Full Changelog: https://github.com/grafana/beyla/compare/v1.0.2...v1.2.0
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
<!-- Release notes generated using configuration in .github/release.yml at main -->
Test release from main
<!-- Release notes generated using configuration in .github/release.yml at main -->
Full Changelog: https://github.com/grafana/beyla/compare/v1.0.0...v1.1.0
<!-- Release notes generated using configuration in .github/release.yml at v1.0.2 -->
<!-- Release notes generated using configuration in .github/release.yml at v1.0.2 -->
Full Changelog: https://github.com/grafana/beyla/compare/v1.0.1...v1.0.2
Thank you for the good reception of Beyla 1.0.0!! Your feedback was very valuable and helped us spotting some bugs that are being fixed with this vers
Thank you for the good reception of Beyla 1.0.0!! Your feedback was very valuable and helped us spotting some bugs that are being fixed with this version 1.0.1.
1.20.5 X:buildcrypto) by @mariomac in https://github.com/grafana/beyla/pull/450Full Changelog: https://github.com/grafana/beyla/compare/v1.0.0...v1.0.1
Nothing published for this version
Nothing published for this version
Nothing published for this version
Grafana Beyla reached version 1.0!!
Grafana Beyla reached version 1.0!!
Check our Grafana Blog for a human-friendly description of its changes: https://grafana.com/blog/2023/11/14/grafana-beyla-1.0-release-zero-code-instrumentation-for-application-telemetry-using-ebpf/
Below, some log-like changes since the last release.
Full Changelog: https://github.com/grafana/beyla/compare/v0.4.2...v1.0.0
<!-- Release notes generated using configuration in .github/release.yml at main -->
<!-- Release notes generated using configuration in .github/release.yml at main -->
make docs procedure by @github-actions in https://github.com/grafana/beyla/pull/426Full Changelog: https://github.com/grafana/beyla/compare/v0.4.1...v0.4.2
Nothing published for this version
One column per quarter.