Ability to re-enable loggers in logging integration

We can disable loggers using ignore_logger but we cannot re-enable them.

The use case I have is the following code

try:
    blob_service.get_blob_to_path(storage_container, blob, local_path)
except AzureMissingResourceHttpError:
    logging.debug(...)

Running this code and running into a AzureMissingResourceHttpError error shows up in sentry because get_blob_to_path logs an error into its own logger (azure.storage.common.storageclient).

Since I found no clean way to filter this in before_send (I thought about setting a flag that we’re handling the error ourselves), I would like to disable and re-enable the logger around this call.

Would this be possible (open to a PR?) or is there a better solution?

Thanks

[untitaker]

Those warnings are insignificant and gone in the latest version of the SDK. It’s a deprecation warning where this code:

init(integrations=[FooIntegration()])
init(integrations=[BarIntegration()])

used to cause Foo and Bar to be enabled in old versions while new SDK versions only enable Bar.

[EvertEt]

Using with sentry_sdk.Hub(None): works perfectly for what I needed, thank you!