getsentry / getsentry/sentry-python
Double-check that `set_transaction_name` is set early enough
Open
Python
- Dominant language
- Python
- Stars
- 2.2k
- Forks
- 669
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 213
Description
In the new major, in our WSGI and ASGI integrations we used to rely on the event processor to set the correct transaction name. We had to move the transaction name setting to the patches in the scope of the span streaming refactor. Verify that we haven't missed any cases (errors captured too early, etc.) where we wouldn't attach the correct transaction name.
Contributor guide
Assessment
This issue has not been assessed yet.