From bc901c69e42621aea98c75623ec659f6c0853792 Mon Sep 17 00:00:00 2001 From: Julian Bez Date: Fri, 6 Nov 2026 17:18:45 +0100 Subject: [PATCH] fix(devex): keep the admin console audit log at info The posthoganalytics SDK claims the "posthog" logger name and clamps it to WARNING. The console writes its audit lines (operation started/finished, with the actor and the reason staff gave) at INFO under posthog.admin.console, so none of them reached the logs. Give the console package its own INFO level, the same way other INFO diagnostics under posthog.* already do. Found by Dan Marchuk in #130856. --- posthog/settings/logs.py | 2 ++ 1 file changed, 2 insertions(+) diff --git a/posthog/settings/logs.py b/posthog/settings/logs.py index 859088a3756a..3d17a8051bcc 100644 --- a/posthog/settings/logs.py +++ b/posthog/settings/logs.py @@ -192,6 +192,8 @@ def add_otel_trace_context( "posthog.api_queries_budget": {"level": "INFO", "handlers": ["console"], "propagate": False}, # Same clamp: the signed-out-with-session-cookie diagnostic in posthog/utils.py logs at INFO. "posthog.utils": {"level": "INFO", "handlers": ["console"], "propagate": False}, + # Same clamp: the admin console audit log, with the reason staff gave, logs at INFO. + "posthog.admin.console": {"level": "INFO", "handlers": ["console"], "propagate": False}, "products.warehouse_sources.backend.temporal.data_imports.pipelines.pipeline_v3.load": { "level": "DEBUG", "handlers": ["console"],