Today we merged a fairly hefty change into the Python SDK. This change replaces the legacy “culprit” concept with a transaction-based contextual name.
For example, in Django, if you’re processing a web request when an error is hit, the transaction name becomes a normalized version of the route pattern. In Celery, this becomes the registered name for the given task. In Flask, similar to Django, its the pattern expression:
This isn’t in a released version of any SDK yet, and is only implemented in Python, but if you’re eager to give it a whirl we’d love to hear your freedback.