An issue I'm having is that the most poorly performing areas of my application appear as "Missing Instrumentation" on the Sentry performance page.

I understand that I can manually add the code to capture these traces, but I have no idea where to include that code. The trace doesn't give me the method that it came from, the module that it belongs to, or any clues as to where I implement the manual tracing code.

Additionally, it looks like many of the missing frames are from Django Rest Framework, which I can't easily wrap with manual transaction capturing.

It would be helpful if the missing areas had some sort of indication as to where they came from. It would also be very helpful if commonly used libraries like encode/django-rest-framework had default performance tracing integration out-of-the-box.