Anton Pirker
Anton Pirker
Right now we also include the name of the library that does the enqueuing in the op. See: https://github.com/getsentry/sentry-python/blob/antonpirker/django-caching-module/sentry_sdk/consts.py#L267-L273 Should we continue to do so or is `messaging.system` span data...
Python SDK tries the following things: * `release` parameter * `SENTRY_RELEASE` env variable * Output of `git rev-parse HEAD` see: https://github.com/getsentry/sentry-python/blob/master/sentry_sdk/utils.py#L59-L95
Not needed anymore. Will close this
@shakfu your stated scenario is the same issue.
Could this be done in `relay` so it works for all SDKs?
Will this change some data available after the with block? (sorry for asking again, I know we have talked this through yesterday, but cant remember the outcome)
This is probably a bug that is worth looking into. Putting it in the internal backlog at low priority
Has perl even a logo or icon @kerenkhatiwada ?
Cool! Thanks for fixing!
I added a link to the relevant custom instrumentation docs in our dramatiq docs: https://github.com/getsentry/sentry-docs/pull/11224