-
Notifications
You must be signed in to change notification settings - Fork 622
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
Profiling issue for Java pods with auto-instumentation method #3730
Comments
Please provide the following:
|
Hi @korniltsev PFB details :
|
Hi @korniltsev |
I'm sorry I did not have time to look into this yet. I may have time to look into this next week. CC @aleks-p just in case :) feel free to look in to this as well if you want to. |
Hi Team, |
HI @korniltsev @aleks-p |
Describe the bug
I am using Java Profiling with Alloy (auto-instrumentation method) for enabling profiling on java pods within cluster. Deployed pyroscope and alloy separately using helm chart and have added below config in alloy configmap for java profiling as provided on below link -
https://github.com/grafana/pyroscope/tree/main/examples/grafana-agent-auto-instrumentation/java/kubernetes
But profiling starts on only few random java pods and not on all java pods. Not able to identify that why profiling is not enabled on all java pods.
Expected behavior
As per documentation on below link all pre-requisites are done at alloy end in helm chart - so not seems issue from alloy end as some pods starts profiling as well and that data is visible in grafana
https://grafana.com/docs/alloy/latest/reference/components/pyroscope/pyroscope.java/
So expected behaviour is that all java pods should start profiling upon adding above config in alloy configmap.
Environment
Additional Context
content: |
The text was updated successfully, but these errors were encountered: