Description

DISCLAIMER: We patched django using a middleware to fix this and wanted to contribute it back to sentry, delegated this to copilot and it looks ok, no intention to be ai-slop, just wanted to raise the issue here.

Django-ninja endpoints were all grouped under ninja.operation.PathView._sync_view when using transaction_style="function_name", making it impossible to distinguish between different API endpoints in Sentry.

Django's resolve() returns the PathView wrapper function instead of the actual endpoint. The wrapper is shared across all endpoints on the same path, causing the grouping issue.

Changes

• Added _unwrap_django_ninja_view() - Detects PathView wrappers by checking __qualname__, extracts the PathView instance from the closure, matches the HTTP method to the correct Operation, and returns the actual endpoint function
• Modified _set_transaction_name_and_source() - Calls unwrapper when transaction_style="function_name" before extracting the transaction name
• Added integration tests - Validates both function_name and url transaction styles work correctly with ninja endpoints

Example

Before this change, all these endpoints would be grouped as ninja.operation.PathView._sync_view:

@api.get("/users")
def list_users(request):
 ...
@api.post("/users")
def create_user(request):
 ...

After this change, they get distinct names: myapp.views.list_users and myapp.views.create_user.