Stop Sentry from swallowing log messages

For a pre-defined set of loggers, like the Gunicorn loggers, Sentry will register itself and disable propagation. However, this means any handlers registered on the root level, like custom formatting stream loggers or forwarding to central log aggregation will no longer get to see these messages.
blue-yonder · Aug 17, 2018 · 7d91ffb · 7d91ffb
1 parent c8fb761
commit 7d91ffb
Show file tree

Hide file tree

Showing 2 changed files with 6 additions and 1 deletion.
diff --git a/CHANGES.rst b/CHANGES.rst
@@ -2,6 +2,11 @@
 Changelog
 =========
 
+UNRELEASED
+==========
+
+- Fix log messages of Gunicorn and Flask not ending up in the root logger.
+
 v2.0.2
 ======
 

diff --git a/postgraas_server/create_app.py b/postgraas_server/create_app.py
@@ -14,7 +14,7 @@
     'SQLALCHEMY_MAX_OVERFLOW'
 ]
 
-sentry = Sentry(logging=True, level=logging.WARN, wrap_wsgi=True)
+sentry = Sentry(logging=True, level=logging.WARN, wrap_wsgi=True, logging_exclusions=())
 
 
 def create_app(config):