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
This breaking change would only affect users configuring Beyla to report internal metrics of its own Behavior (mainly used for performance testing and…
Beyla 1.7.0 is out with a huge amount of features and bugfixes!
Please check the Beyla documentation for more information about how to configure and enable them: https://grafana.com/docs/beyla/latest/
This breaking change would only affect users configuring Beyla to report internal metrics of its own Behavior (mainly used for performance testing and debugging purposes)
Replaces the bfp_debug configuration option by bpf_debug. This option is mainly used by Beyla developers for internal debugging.
The user still has the possibility to disable them by means of the attributes selection YAML section.
The user still has the possibility to disable heuristic routes in the routes YAML configuration.
⚠️ This feature is based in the current OpenTelemetry semantic convention for OS Processes, which is currently marked as Experimental. You might expect some breaking changes in the future.
Add application_process to the BEYLA_OTEL_METRIC_FEATURES or BEYLA_PROMETHEUS_FEATURES option to get the following Process metrics:
process.cpu.timeprocess.cpu.utilizationprocess.memory.usageprocess.memory.virtualprocess.disk.ioprocess.network.ioBeyla now supports the following application protocols for both Go programs:
client.port and server.port attributesNetwork metrics bring src.port and dst.port, which would be swapped in request and response network metrics. client.port and server.port remain consistent for both request and response network metrics.
make docs procedure by @github-actions in https://github.com/grafana/beyla/pull/888make docs procedure by @github-actions in https://github.com/grafana/beyla/pull/979Full Changelog: https://github.com/grafana/beyla/compare/v1.6.4...v1.7.0
Your coding agent can read these notes before it upgrades. Set up the MCP server →
Defining the OTEL_EXPORTER_OTLP_TRACES_ENDPOINT with the /v1/traces suffix (as expected by the OpenTelemetry definition) caused that the url defined t
Defining the OTEL_EXPORTER_OTLP_TRACES_ENDPOINT with the /v1/traces suffix (as expected by the OpenTelemetry definition) caused that the url defined that path twice.
Beyla 1.6.4 fixes that situation.
<!-- Release notes generated using configuration in .github/release.yml at release-1.6 -->
<!-- Release notes generated using configuration in .github/release.yml at release-1.6 -->
Full Changelog: https://github.com/grafana/beyla/compare/v1.6.2...v1.6.3
Restore service.name as metric attribute (1.6 backport) by @mariomac in https://github.com/grafana/beyla/pull/869
Full Changelog: https://github.com/grafana/beyla/compare/v1.6.1...v1.6.2
Fixes an array index panic during SQL parsing by @mariomac in https://github.com/grafana/beyla/pull/857
Fixes an array index panic during SQL parsing by @mariomac in https://github.com/grafana/beyla/pull/857
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
Now traces prefer the peer hostname over the IP addres. This could affect you if you have any alert or dashboard relying in the old IP-based peer addr
Now traces prefer the peer hostname over the IP addres. This could affect you if you have any alert or dashboard relying in the old IP-based peer address.
Beyla 1.5 allowed to select which attributes were reported in the network metrics.
Beyla 1.6 extends this feature to application-level metrics. For example:
attributes:
select:
beyla_network_flow_bytes:
# limit the beyla_network_flow_bytes attributes to only the three attributes
include:
- beyla.ip
- src.name
- dst.port
sql_client_duration:
# report all the possible attributes but db_statement
include: ["*"]
exclude: ["db_statement"]
http_client_request_duration:
# report the default attribute set but exclude the Kubernetes Pod information
exclude: ["k8s.pod.*"]
Check the documentation for more details.
Beyla 1.6 lets filtering out metrics and spans not matching the provided selection criteria.
For example:
filter:
network:
transport: UDP
dst_port: "53"
Would cause that beyla only reports UDP network flows whose destination port is 53.
It allows to match multiple values by with a filesystem-like Glob syntax. For example:
filter:
application:
k8s.pod.name: beyla-*
Would report only application metrics and traces from Kubernetes pods whose name starts with beyla-.
Check the documentation for more details.
To reduce cardinality of Application metrics in Prometheus, Beyla will stop reporting the metrics of an application between two endpoints when there is unobserved activity during 5 minutes. You can override the default 5-minutes value with the BEYLA_PROMETHEUS_TTL configuration options.
This feature was already available in Beyla 1.5 for network metrics exported via OTEL or Prometheus. However, the expiration is not yet available for Application observability with OpenTelemetry, as the OpenTelemetry SDK does not yet provide a feasible way to remove histogram metrics.
In order to enforce our compatibility with opentelemetry standards, the OTEL_GO_AUTO_TARGET_EXE configuration option is now supported.
This environment variable is equivalent to the BEYLA_EXECUTABLE_NAME environment variable.
When network metrics are sent via Prometheus or via an intermadiate OTEL collector, the metrics are queryable as beyla_network_flow_metrics_total in Grafana.
Before this release, when using the OTEL endpoint in Grafana Cloud, metrics were visible as beyla_network_flow_metrics, without the _total.
Beyla 1.6.0 adds explicitly the .total suffix to the OTEL exporter.
make docs procedure by @github-actions in https://github.com/grafana/beyla/pull/772n in bufio.Writer offset with naming variable by @titaneric in https://github.com/grafana/beyla/pull/833make docs procedure by @github-actions in https://github.com/grafana/beyla/pull/842Full Changelog: https://github.com/grafana/beyla/compare/v1.5.3...v1.6.0
<!-- Release notes generated using configuration in .github/release.yml at release-1.5 -->
<!-- Release notes generated using configuration in .github/release.yml at release-1.5 -->
Full Changelog: https://github.com/grafana/beyla/compare/v1.5.2...v1.5.3
<!-- Release notes generated using configuration in .github/release.yml at release-1.5 -->
<!-- Release notes generated using configuration in .github/release.yml at release-1.5 -->
Full Changelog: https://github.com/grafana/beyla/compare/v1.5.1...v1.5.2
<!-- Release notes generated using configuration in .github/release.yml at release-1.5 -->
<!-- Release notes generated using configuration in .github/release.yml at release-1.5 -->
Fixes a bug introduced in Beyla 1.5.0 that could cause some that Go gRPC instrumented services stopped working.
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
> ⚠️ Network metrics is still an experimental feature under active development. Expect breaking changes in future Beyla versions.
This change adds a new selector property k8s_pod_labels to the discovery.services configuration section. This selector property will limit the instrumentation to the applications running in the Pods having labels with matching keys and values.
Kudos for @msvechla for its contribution.
Beyla 1.5 can generate application metrics in span metrics/service graph format directly, replicating how metrics are derived from application traces. This allows for better support and integration with products which rely on span metrics, such as Grafana Cloud Application Observability, where the application traces are sampled, and therefore the span metrics are inaccurate.
To enable span or service graph metrics, add the application_span or application_service_graph values to the BEYLA_OTEL_METRICS_FEATURES or BEYLA_PROMETHEUS_FEATURES configuration properties. Check the Beyla configuration documentation for more details.
⚠️ Network metrics is still an experimental feature under active development. Expect breaking changes in future Beyla versions.
Network metrics now can be exported as Prometheus, as an alternative to OpenTelemetry. To enable it, just set the BEYLA_PROMETHEUS_PORT configuration value when BEYLA_NETWORK_METRICS is enabled.
You can filter metrics by Internet protocol. For example, you could restrict the network metrics only to UDP traffic. The BEYLA_NETWORK_PROTOCOLS and BEYLA_NETWORK_EXCLUDE_PROTOCOLS will let you enumerate which protocols to accept
or exclude.
To reduce cardinality of Network metrics, either in Prometheus or OpenTelemetry, Beyla will stop reporting the network metrics between two endpoints when there is unobserved traffic between both endpoints during 5 minutes. You can override the default 5-minutes value with the BEYLA_OTEL_METRICS_TTL or BEYLA_PROMETHEUS_TTL configuration options. This feature is not yet available for application-level metrics.
Finally, the following attributes can be now added to the network metrics: src.port, dst.port and transport.
Check documentation for more configuration details.
Fixed a bug present in previous versions of Beyla, that prevented Beyla from properly measuring the response time of long responses (for example, a data stream or downloading a large file).
sql.Exec by @marctc in https://github.com/grafana/beyla/pull/733Full Changelog: https://github.com/grafana/beyla/compare/v1.4.1...v1.5.0
<!-- Release notes generated using configuration in .github/release.yml at release-1.4 -->
<!-- Release notes generated using configuration in .github/release.yml at release-1.4 -->
Full Changelog: https://github.com/grafana/beyla/compare/v1.5.0...v1.4.2
<!-- Release notes generated using configuration in .github/release.yml at release-1.4 -->
<!-- Release notes generated using configuration in .github/release.yml at release-1.4 -->
Full Changelog: https://github.com/grafana/beyla/compare/v1.4.0...v1.4.1
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
One column per quarter.