Skip to content

:hedgehog: PostHog is the leading platform for building self-driving products. Our developer tools – AI observability, analytics, session replay, flags, experiments, error tracking, logs, and more – capture all the context agents need to diagnose problems, uncover opportunities, and ship fixes. Steer it all from Slack, web, desktop, or the MCP.

fix(replay): log snapshot cap overruns at warning so they reach production logs (#130177)

Paul D'Ambra3dfc0974ca7c
diff --git a/posthog/session_recordings/session_recording_api.py b/posthog/session_recordings/session_recording_api.py
index d60dfa600dd2..6c2207225a07 100644
--- a/posthog/session_recordings/session_recording_api.py
+++ b/posthog/session_recordings/session_recording_api.py
@@ -992,7 +992,8 @@ class _SnapshotUserRateThrottle(SimpleRateThrottle):
_count_session_recording_throttled(location=location, auth_type=_request_auth_type(request))
# A client over the limit stays over it for every later request, so log once a minute per user, not per request.
if cache.add(f"{self.scope}_logged:{request.user.pk}", 1, timeout=60):
- logger.info(
+ # Warning, not info: production drops INFO from this logger, and this line is how we see who goes over.
+ logger.warning(
"snapshot_user_rate_limit_exceeded",
scope=self.scope,
enforced=enforced,