Is your feature request related to a problem? Please describe.
Today one may get profiling results via the debug endpoint that we stand up for every go pod.
While there is some massaging of time frames and the like that we want to use per issue we should at least publicize and maximally wrap deploy based retrievals.
Describe the solution you'd like
glooctl debug pprof
which would generate outputs for all pods and would optionally take a deployment name to only get the specified pod.
Often when we ask for performance stats we are looking at a single pod so something like
glooctl debug pprof gloo
or
glooctl pprof gloo
would then output cpu profile, heap and various other dumps that could then be shared.
This issue has been marked as stale because of no activity in the last 180 days. It will be closed in the next 180 days unless it is tagged "no stalebot" or other activity occurs.
Gloo Edge Product
Open Source
Gloo Edge Version
1.15.x
Is your feature request related to a problem? Please describe.
Today one may get profiling results via the debug endpoint that we stand up for every go pod. While there is some massaging of time frames and the like that we want to use per issue we should at least publicize and maximally wrap deploy based retrievals.
Describe the solution you'd like
glooctl debug pprof which would generate outputs for all pods and would optionally take a deployment name to only get the specified pod.
Often when we ask for performance stats we are looking at a single pod so something like
glooctl debug pprof gloo or glooctl pprof gloo
would then output cpu profile, heap and various other dumps that could then be shared.
Describe alternatives you've considered
No response
Additional Context
No response