You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a Go application (inspektor-gadget/inspektor-gadget#3992) that can potentially run several independent WASM modules with wazero. I am trying to use wzprof to expose pprof on a single TCP port, but it does not seem supported:
wzprof.Handler() is instantiated for a specific Profiling instance. I cannot call wzprof.ProfilingFor multiple times for a single http handler.
wzprof.Handler() cannot use a different path than "/debug/pprof/" because the handler would fail on pprof.go#L146 (strings.CutPrefix), so I cannot use several http handlers on separate URLs for different WASM modules.
At the moment, I listen on a different TCP port for each WASM module. Is it possible to use wzprof.Handler() in a different way to avoid using different TCP ports?
The text was updated successfully, but these errors were encountered:
I have a Go application (inspektor-gadget/inspektor-gadget#3992) that can potentially run several independent WASM modules with wazero. I am trying to use wzprof to expose pprof on a single TCP port, but it does not seem supported:
wzprof.Handler()
is instantiated for a specificProfiling
instance. I cannot callwzprof.ProfilingFor
multiple times for a single http handler.wzprof.Handler()
cannot use a different path than "/debug/pprof/" because the handler would fail on pprof.go#L146 (strings.CutPrefix), so I cannot use several http handlers on separate URLs for different WASM modules.At the moment, I listen on a different TCP port for each WASM module. Is it possible to use
wzprof.Handler()
in a different way to avoid using different TCP ports?The text was updated successfully, but these errors were encountered: