Menu

Important: This documentation is about an older version. It's relevant only to the release noted, many of the features and functions have been updated or replaced. Please view the current version.

Documentationbreadcrumb arrow Beylabreadcrumb arrow Exported metrics
Grafana Cloud

Beyla exported metrics

The following table describes the exported metrics in both OpenTelemetry and Prometheus format.

FamilyName (OTEL)Name (Prometheus)TypeUnitDescription
Applicationhttp.client.request.durationhttp_client_request_duration_secondsHistogramsecondsDuration of HTTP service calls from the client side
Applicationhttp.client.request.body.sizehttp_client_request_body_size_bytesHistogrambytesSize of the HTTP request body as sent by the client
Applicationhttp.server.request.durationhttp_server_request_duration_secondsHistogramsecondsDuration of HTTP service calls from the server side
Applicationhttp.server.request.body.sizehttp_server_request_body_size_bytesHistogrambytesSize of the HTTP request body as received at the server side
Applicationrpc.client.durationrpc_client_duration_secondsHistogramsecondsDuration of GRPC service calls from the client side
Applicationrpc.server.durationrpc_server_duration_secondsHistogramsecondsDuration of RPC service calls from the server side
Applicationsql.client.durationsql_client_duration_secondsHistogramsecondsDuration of SQL client operations (Experimental)
Networkbeyla.network.flow.bytesbeyla_network_flow_bytesCounterbytesBytes submitted from a source network endpoint to a destination network endpoint

Beyla can also export Span metrics and Service graph metrics, which can be enabled via the features configuration option.

Attributes of Beyla metrics

For the sake of brevity, only the OTEL dot.notation of the metrics and attributes is listed, but the metrics and attributes are exposed underscore_notation when a Prometheus exporter is used.

In order to hide attributes that are shown by default, or show attributes that are hidden by default, check the attributes->select section in the configuration documentation.

MetricsNameDefault
Application (all)http.request.methodshown
Application (all)http.response.status_codeshown
Application (all)http.routeshown if routes configuration is defined
Application (all)k8s.daemonset.nameshown if attributes.kubernetes.enable
Application (all)k8s.deployment.nameshown if attributes.kubernetes.enable
Application (all)k8s.namespace.nameshown if attributes.kubernetes.enable
Application (all)k8s.node.nameshown if attributes.kubernetes.enable
Application (all)k8s.pod.nameshown if attributes.kubernetes.enable
Application (all)k8s.pod.start_timeshown if attributes.kubernetes.enable
Application (all)k8s.pod.uidshown if attributes.kubernetes.enable
Application (all)k8s.replicaset.nameshown if attributes.kubernetes.enable
Application (all)k8s.statefulset.nameshown if attributes.kubernetes.enable
Application (all)service.nameshown
Application (all)service.namespaceshown
Application (all)target.instanceshown
Application (all)url.pathhidden
Application (client)server.addresshidden
Application (client)server.porthidden
Application rpc.*rpc.grpc.status_codeshown
Application rpc.*rpc.methodshown
Application rpc.*rpc.systemshown
Application (server)client.addresshidden
beyla.network.flow.bytesbeyla.iphidden
sql.client.durationdb.operationshown
sql.client.durationdb.statementshown
beyla.network.flow.bytesdirectionhidden
beyla.network.flow.bytesdst.addresshidden
beyla.network.flow.bytesdst.cidrshown if the cidrs configuration is defined
beyla.network.flow.bytesdst.namehidden
beyla.network.flow.bytesdst.porthidden
beyla.network.flow.bytesifacehidden
beyla.network.flow.bytesk8s.cluster.nameshown if attributes.kubernetes.enable
beyla.network.flow.bytesk8s.dst.namehidden
beyla.network.flow.bytesk8s.dst.namespaceshown if attributes.kubernetes.enable
beyla.network.flow.bytesk8s.dst.node.iphidden
beyla.network.flow.bytesk8s.dst.node.namehidden
beyla.network.flow.bytesk8s.dst.owner.typehidden
beyla.network.flow.bytesk8s.dst.typehidden
beyla.network.flow.bytesk8s.dst.owner.nameshown if attributes.kubernetes.enable
beyla.network.flow.bytesk8s.src.namehidden
beyla.network.flow.bytesk8s.src.namespaceshown if attributes.kubernetes.enable
beyla.network.flow.bytesk8s.src.node.iphidden
beyla.network.flow.bytesk8s.src.owner.nameshown if attributes.kubernetes.enable
beyla.network.flow.bytesk8s.src.owner.typehidden
beyla.network.flow.bytesk8s.src.typehidden
beyla.network.flow.bytessrc.addresshidden
beyla.network.flow.bytessrc.cidrshown if the cidrs configuration is defined
beyla.network.flow.bytessrc.namehidden
beyla.network.flow.bytessrc.porthidden
beyla.network.flow.bytestransporthidden

Internal metrics

Beyla can be configured to report internal metrics in Prometheus Format.

NameTypeDescription
ebpf_tracer_flushesHistogramLength of the groups of traces flushed from the eBPF tracer to the next pipeline stage
otel_metric_exportsCounterLength of the metric batches submitted to the remote OTEL collector
otel_metric_export_errorsCounterVecError count on each failed OTEL metric export, by error type
otel_trace_exportsCounterLength of the trace batches submitted to the remote OTEL collector
otel_trace_export_errorsCounterVecError count on each failed OTEL trace export, by error type
prometheus_http_requestsCounterVecNumber of requests towards the Prometheus Scrape endpoint, faceted by HTTP port and path