simple sky
Hi everyone,
I’m facing an issue with Sentry profiling in our self-hosted setup. We’ve enabled profiling for Resque background jobs, but I’ve noticed two challenges:
1. Sentry seems to be using the same thread to send the profiling traces, which is causing longer execution times for the background jobs. How can I move Sentry profiling out of the main job thread and handle it in a separate background job?
2. Even though the profiling traces are being sent to Sentry (I can confirm they’re sent over the wire), no profiles are visible in the Sentry UI for background jobs. However, profiling works as expected for the frontend and backend.
Has anyone encountered a similar issue? Any advice on fixing these two problems?
Thanks in advance!
fresh phoenix
