SentryAsgiMiddleware doesn't set the "message" field in FastAPI

I don’ know why exactly, but SentryAsgiMiddleware doesn’t set the “message” field in FastAPI. In result, all events have title <no message value> in issues feed. I managed to fix problem through this code:

def before_send(event, hint):
    error_name = event['exception']['values'][0]['type']
    event.update({"message": error_name})
    return event

All parts except this one are working great (so far) and I very appreciate this library, but I don’ think this is expected behavior.

[untitaker]

Right but you have logentry in there, that is supposed to be shown instead. Sentry 10 deprecates message in favor of logentry. If you want the Sentry 10 behavior I suggest copying event['logentry']['message'] into event['message'] (but you can do whatever you want to set the issue title to what you prefer)

We support old SDKs in newer Sentry, but not newer SDKs in older Sentry. To enable support we would have to send the message attribute as well as logentry. I think we could add something to the SDK to enable support for older Sentries, but it would be a kind of option or an integration of some sort and definetly community maintained.

I recommend updating to Sentry 9 at least.

[kozhushman]

Oh, I see! Thanks for the clarification! I can’t influence the Sentry update, but now i know what is happening 😃 In my case

copying event[‘logentry’][‘message’] into event[‘message’]

won’t work, because it’s just saying "Exception in ASGI application\n" instead of real exception