search

grafana / beyla

eBPF-based autoinstrumentation of web applications and network metrics
https://grafana.com/oss/beyla-ebpf/
Apache License 2.0
1.44k stars 102 forks source link

Beyla with Helm Error #1229

Open inexactt opened 1 month ago

inexactt commented 1 month ago

I'm trying to install Beyla with Helm in a Minikube Cluster running with Docker but i'm receiving an error, im not overriding any configuration

I executed this command

helm install beyla -n beyla --create-namespace  grafana/beyla

Error

> kubectl logs beyla-czm7s -n beyla
time=2024-10-04T22:54:16.091Z level=INFO msg="Grafana Beyla" Version=98352a76 Revision=98352a76 "OpenTelemetry SDK Version"=1.28.0
time=2024-10-04T22:54:16.604Z level=INFO msg="got host ID" component=ContextInfo func=fetchHostID fetcher=KubeNode hostID=1e8c6012565847749d92e9f05d8935f6
time=2024-10-04T22:54:16.604Z level=INFO msg="starting Beyla in Application Observability mode"
time=2024-10-04T22:54:16.710Z level=INFO msg="using hostname" component=traces.ReadDecorator function=instance_ID_hostNamePIDDecorator hostname=beyla-czm7s
time=2024-10-04T22:54:17.150Z level=INFO msg="instrumenting process" component=discover.TraceAttacher cmd=/usr/local/bin/ruby pid=10849
time=2024-10-04T22:54:19.244Z level=WARN msg="can't fetch Kubernetes Cluster Name. Network metrics won't contain k8s.cluster.name attribute unless you explicitly set  the BEYLA_KUBE_CLUSTER_NAME environment variable" component=transform.KubernetesDecorator func=KubeClusterName
time=2024-10-04T22:54:19.244Z level=ERROR msg="Beyla can't start" error="can't start read and forwarding: can't instantiate instrumentation pipeline: invoking Middle node provider: error invoking provider: attribute filter: unknown attribute name "client""

I'm following this grafana documentation https://grafana.com/docs/beyla/latest/setup/kubernetes-helm/

seeingidog2 commented 1 month ago

Seeing the same thing. Regression from this PR.

grcevski commented 1 month ago

Sorry about that, we didn't realize the helm chart had a dependency on our main branch, we need to do this better. We are working on a revert of that PR and we'll publish a new helm chart update.

mariomac commented 1 month ago

Reverting the regression PR: https://github.com/grafana/beyla/pull/1231 and publishing as 1.4.3 https://github.com/grafana/beyla/pull/1233

The failing helm chart had sense and might work under some non-default configuration.

This issue is actually a mistake in Beyla. Beyla returns error because the client attribute of the filter is not recognized as an attribute in RED metrics, but the client attribute is already present in some application metrics such as service graph metrics.