-
Notifications
You must be signed in to change notification settings - Fork 239
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
Pyroscope Java profiling not working after following documentation (missing Linux capabilities) #1616
Comments
Adding the following allows the container to read what it needs:
Is it documented anywhere which capabilities are required for Alloy to function? Thanks |
Hi @korniltsev! The only thing I can see in that documentation is a note about requiring root and running inside the host pid namespace, but that is not necessarily sufficient for things to work if linux capabilities are enabled (of which they will usually be in any well-configured production environment). Took a little trial and error, but we found that the following was sufficient for our use case (using Grafana Alloy only to scrape data for Pyroscope):
Hopefully this issue will help anyone else running into the same problem. |
We usually run it as "privileged" root. |
What's wrong?
After following the documentation here, profiling of Java processes results in the following errors for all processes:
Helm values:
Alloy config:
Steps to reproduce
Install Alloy in a Kubernetes cluster using the above values and configuration
System information
Linux version 5.10.223-212.873.amzn2.x86_64
Software version
Grafana Alloy v1.3.1
Configuration
Logs
The text was updated successfully, but these errors were encountered: