Conversation
A cron worker serves no WSGI request, so the middleware that scopes HTTP requests never covers it. Its jobs keep the scope built when the SDK was initialized, before the workers forked, so events from unrelated jobs report the same trace and carry each other's breadcrumbs. Fork the scope in ir.cron._callback and drop the trace and breadcrumbs that forking keeps.
Contributor
|
Hi @fernandahf, @barsi, @naglis, @versada, |
A queue job runs inside an HTTP request, so it already gets a scope of its own, but it is reported under the route that ran it and every job groups under that one name. Name it after the job instead. Only when queue_job is available, the way the module already treats server_environment.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A cron worker serves no WSGI request, so the middleware that scopes HTTP requests never covers it. Its jobs keep the scope built when the SDK was initialized, before the workers forked, so events from unrelated jobs report the same trace and carry each other's breadcrumbs.
Fork the scope in ir.cron._callback and drop the trace and breadcrumbs that forking keeps.