Context "leaking" between Flask apps

(After a few exchanges with support, I was told to post my issue here and tag @untitaker)

Our application serves multiple flask apps via subdomain dispatching.

I am noticing that the context/tags set in one app are occasionally “leaking” over into the others, as if the sentry context is not always isolated between apps. Hopefully I am just configuring something wrong, but I don’t believe our set-up is especially complicated.

A brief example/summary: One Flask app runs our API routes/logic and another runs our web admin interface. Both apps have before_request hooks that set a Sentry tag called “interface” to either "api" or "admin". In general, all issues/errors triggered in the API app show up in Sentry with the correct “interface” tag value (api), and same with the admin issues. However, occasionally, there are, for example, issues triggered in the admin app that appear in Sentry tagged with "api". Additionally, the transaction value is completely mismatched with the url value (for that given event).

Any guidance here? Let me know what other details I can provide to help debug. I can provide links to relevant Sentry issues/events in private communication.

[untitaker]

@michaelbukachi this was a bug in the SDK and has been resolved in 0.6.3. I am quite certain your issue is unrelated. Please file a new issue or ask on StackOverflow.

[michaelbukachi]

@ibushong I’m curious to know how you implemented sentry for each app. Currently doing a similar setup and but we are kinda stuck. We keep getting a

Warning: Integration <class 'sentry_sdk.integrations.stdlib.StdlibIntegration'> attempted to run but it was only enabled on init() but not the client that was bound to the current flow.  Earlier versions of the SDK would consider these integrations enabled but this is no longer the case.