From 8a29aefd47e7ed840dfc8a248e5c83194f9fac07 Mon Sep 17 00:00:00 2001 From: Ivana Kellyer Date: Thu, 20 Nov 2025 16:21:24 +0100 Subject: [PATCH 1/3] feat(loguru): Introduce a troubleshooting section Add a Troubleshooting section with common gotchas one might run into when using Loguru. --- .../platforms/python/integrations/loguru/index.mdx | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/docs/platforms/python/integrations/loguru/index.mdx b/docs/platforms/python/integrations/loguru/index.mdx index 2232cb4b52f6fb..9c87de7947b5b1 100644 --- a/docs/platforms/python/integrations/loguru/index.mdx +++ b/docs/platforms/python/integrations/loguru/index.mdx @@ -174,6 +174,20 @@ sentry_sdk.init( Default: `ERROR` +## Troubleshooting + + + + First, make sure you have the `enable_logs=True` option in your `sentry_sdk.init()`. + + Your logs could be missing because of logging level mismatches between your Loguru setup and your Sentry options. The SDK will honor the configured level of each logger. That means that you won't see any `INFO` or `DEBUG` data in Sentry from a logger with the level set to `WARNING`, regardless of how you configure the integration. + + It might also be the case that the SDK's Loguru setup is being overwritten in your app. Sentry plugs into Loguru by adding its own handlers when you call `sentry_sdk.init()`. If those handlers are later overridden, for example by calling `logger.configure(handlers=...)`, the integration won't work. + + Another reason why you might not be seeing your logs in Sentry is because they were rejected client- or server-side. This could be due to them being too large, or because of reasons like rate limits or backpressure management. In Sentry, you can go to `Settings > Stats & Usage` and select `Logs` from the `Category` dropdown to see what logs were dropped. + + + ## Supported Versions - Loguru: 0.5+ From fcada641ee508fb947a5e0bd822bdcf365563c63 Mon Sep 17 00:00:00 2001 From: Ivana Kellyer Date: Thu, 20 Nov 2025 16:36:53 +0100 Subject: [PATCH 2/3] wording --- docs/platforms/python/integrations/loguru/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/platforms/python/integrations/loguru/index.mdx b/docs/platforms/python/integrations/loguru/index.mdx index 9c87de7947b5b1..028e58ccb7da63 100644 --- a/docs/platforms/python/integrations/loguru/index.mdx +++ b/docs/platforms/python/integrations/loguru/index.mdx @@ -180,7 +180,7 @@ sentry_sdk.init( First, make sure you have the `enable_logs=True` option in your `sentry_sdk.init()`. - Your logs could be missing because of logging level mismatches between your Loguru setup and your Sentry options. The SDK will honor the configured level of each logger. That means that you won't see any `INFO` or `DEBUG` data in Sentry from a logger with the level set to `WARNING`, regardless of how you configure the integration. + Your logs could be missing because of the logging level of the logger. The SDK will honor the configured level of each logger. That means that you won't see any `INFO` or `DEBUG` data in Sentry from a logger with the level set to `WARNING`, regardless of how you configure the integration. It might also be the case that the SDK's Loguru setup is being overwritten in your app. Sentry plugs into Loguru by adding its own handlers when you call `sentry_sdk.init()`. If those handlers are later overridden, for example by calling `logger.configure(handlers=...)`, the integration won't work. From c3f37a36c6497d3c0a243d02a132443c04d83a41 Mon Sep 17 00:00:00 2001 From: Ivana Kellyer Date: Thu, 20 Nov 2025 17:50:05 +0100 Subject: [PATCH 3/3] . --- docs/platforms/python/integrations/loguru/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/platforms/python/integrations/loguru/index.mdx b/docs/platforms/python/integrations/loguru/index.mdx index 028e58ccb7da63..44eea66606c369 100644 --- a/docs/platforms/python/integrations/loguru/index.mdx +++ b/docs/platforms/python/integrations/loguru/index.mdx @@ -178,7 +178,7 @@ sentry_sdk.init( - First, make sure you have the `enable_logs=True` option in your `sentry_sdk.init()`. + First, make sure you have the `enable_logs=True` option in your `sentry_sdk.init()` and you're on the latest version of the SDK. Your logs could be missing because of the logging level of the logger. The SDK will honor the configured level of each logger. That means that you won't see any `INFO` or `DEBUG` data in Sentry from a logger with the level set to `WARNING`, regardless of how you configure the integration.