Thanks for the answer.

I also already saw those posts, and nothing came out useful.

However, we came with another approch :

• we added a django middleware that create a thread, and kill the thread when the query is finished
• the thread wait harakiri time - 2 seconds then capture an exception / error message "Query is too long" and finish the transaction (to send to the performance Sentry database)
• 2s later, the request will be harakiried

With this, if a query last less than harakiri time - 2 seconds, the middleware do nothing. If not, the query will be sent to sentry.

It's not the cleanest way to handle this issue, but so far, it's working fine, and we've been able to pinpoint where queries were stucked / looped when harakiri occured.

getsentry/sentry-docs#6428

opening a docs issue. Worth discussing with team if we would want to add something like this there

Thank you! And if you have any specific code snippet examples, it could make it easier to discuss with the team.

The following snippet should work with Django and uWSGI :

timeout_delay = None
try:
    import uwsgi

    if uwsgi_harakiri := uwsgi.opt.get("harakiri", False):
        timeout_delay = int(uwsgi_harakiri) - 2
except ImportError:
    pass


def log_before_harakiri(thread_hub, transaction):
    with thread_hub:
        capture_message("Long request")
    if transaction is not None:
        transaction.finish()
    thread_hub.flush()


class TimeoutMiddleware:
    def __init__(self, get_response):
        self.get_response = get_response

    def __call__(self, request):
        if timeout_delay is None:
            return self.get_response(request)
        thread_hub = sentry_sdk.Hub(sentry_sdk.Hub.current)
        transaction = sentry_sdk.Hub.current.scope.transaction
        harakiri_timer = threading.Timer(
            timeout_delay, log_before_harakiri, args=[thread_hub, transaction]
        )
        harakiri_timer.start()
        try:
            return self.get_response(request)
        finally:
            harakiri_timer.cancel()

However, as-is, there is a drawback as request during between harakiri - 2s and harakiris won't be fully sent to Sentry.

Yes, we could add this to the docs. Maybe we should create a "cook book" section, where we put recipies for common use cases?

I like it :D

would just like to follow something similar to other frameworks, that could also be transparently used in the includes across uWSGI

also I will put on PM hat: uWSGI Framework Features section might have more SEO bump