-
Notifications
You must be signed in to change notification settings - Fork 486
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failure to build 0.27.0 (issues with gobpf/bcc) #2113
Comments
Hey there, thanks for the report. This seems to be another case of For the time being, you could either use the |
I am packaging grafana-agent for ArchLinux. We could disable ebpf, but anyone using that would suddenly either get errors, or have missing metrics. |
Oh, I see, thanks for your efforts! The issue is that the gobpf library needs to match the exact bcc version, that's why they also suggest pinning the gobpf version to follow a single bcc release. Let's see if the upstream issue gains any traction; even then I would be hesitant to upgrade since it would be breaking for other users as well. We're looking into a couple of alternatives for making working with bcc easier. In the meantime, while not ideal, disabling the integration could be a decent tradeoff. Users wouldn't get errors, just missing metrics and a "the ebpf integration is not available; enabling it will do nothing" log line; maybe we should make a better job at letting them understand they'd have to go about building the Agent themselves with the matching bcc version if they want to use this specific integration. |
@tpaschalis the patch suggested in iovisor/gobpf#311 will keep working with older bcc versions as well, just keep using the latest gobpf. |
I'm closing this as If we bring this back, we should look into either using cloudflare/ebpf_exporter's release v2.0 which moves away from BCC or something based on cilium's go-ebpf to avoid such issues with static linking. |
Upstream issue: iovisor/gobpf#314
The text was updated successfully, but these errors were encountered: