Extract wrapped Sidekiq job class names in both Sidekiq integrations#1238
Conversation
This was replaced in getsentry#1177, but the middleware wasn't actually removed.
Codecov Report
@@ Coverage Diff @@
## master #1238 +/- ##
===========================================
- Coverage 97.92% 71.66% -26.26%
===========================================
Files 193 44 -149
Lines 8280 1546 -6734
===========================================
- Hits 8108 1108 -7000
- Misses 172 438 +266
Continue to review full report at Codecov.
|
c74d656 to
841e6ab
Compare
|
I'm not sure why project-level code coverage dropped so significantly, @st0012 let me know if I have something weird going on here that is causing that! |
|
@agrobbin thanks for the PR 👍 it looks good but I'll do some testing to see why I was not able to spot the issue before merging this, which will probably be this Friday 🙂 |
841e6ab to
6cd7bec
Compare
The Active Job `wrapped` job class name logic was only happening in the lower-level `ErrorHandler`, and was actually being ignored since `transaction_name` was already set via `SentryContextMiddleware`. Now, the logic to properly extract the `transaction_name` has been refactored into `ContextFilter`.
6cd7bec to
e372134
Compare
|
@st0012 just pushed an update here, let me know if there's anything else I can do! |
st0012
left a comment
There was a problem hiding this comment.
thanks for the great work 👍
|
Thanks, @st0012! Looking forward to getting this released and into production. |

The Active Job
wrappedjob class name logic was only happening in the lower-levelErrorHandler, and was actually being ignored sincetransaction_namewas already set viaSentryContextMiddleware.Now, the logic to properly extract the
transaction_namehas been refactored into 1Utilclass that is used bySentryContextMiddlewareandErrorHandler.Separately, this removes the now-unused
CleanupMiddleware, after its replacement in #1177.Fixes #1237.