deploy: d27ff161f5

develop/log_contexts.html

@@ -604,6 +604,17 @@ chain are dropped. Dropping the the reference to an awaitable you're
 supposed to be awaiting is bad practice, so this doesn't
 actually happen too much. Unfortunately, when it does happen, it will
 lead to leaked logcontexts which are incredibly hard to track down.</p>
+<h2 id="debugging-logcontext-issues"><a class="header" href="#debugging-logcontext-issues">Debugging logcontext issues</a></h2>
+<p>Debugging logcontext issues can be tricky as leaking or losing a logcontext will surface
+downstream and can point to an unrelated part of the codebase. It's best to enable debug
+logging for <code>synapse.logging.context.debug</code> (needs to be explicitly configured) and go
+backwards in the logs from the point where the issue is observed to find the root cause.</p>
+<p><code>log.config.yaml</code></p>
+<pre><code class="language-yaml">loggers:
+    # Unlike other loggers, this one needs to be explicitly configured to see debug logs.
+    synapse.logging.context.debug:
+        level: DEBUG
+</code></pre>
 
                     </main>
 

develop/print.html

@@ -19681,6 +19681,17 @@ chain are dropped. Dropping the the reference to an awaitable you're
 supposed to be awaiting is bad practice, so this doesn't
 actually happen too much. Unfortunately, when it does happen, it will
 lead to leaked logcontexts which are incredibly hard to track down.</p>
+<h2 id="debugging-logcontext-issues"><a class="header" href="#debugging-logcontext-issues">Debugging logcontext issues</a></h2>
+<p>Debugging logcontext issues can be tricky as leaking or losing a logcontext will surface
+downstream and can point to an unrelated part of the codebase. It's best to enable debug
+logging for <code>synapse.logging.context.debug</code> (needs to be explicitly configured) and go
+backwards in the logs from the point where the issue is observed to find the root cause.</p>
+<p><code>log.config.yaml</code></p>
+<pre><code class="language-yaml">loggers:
+    # Unlike other loggers, this one needs to be explicitly configured to see debug logs.
+    synapse.logging.context.debug:
+        level: DEBUG
+</code></pre>
 <div style="break-before: page; page-break-before: always;"></div><h1 id="replication-architecture"><a class="header" href="#replication-architecture">Replication Architecture</a></h1>
 <h2 id="motivation"><a class="header" href="#motivation">Motivation</a></h2>
 <p>We'd like to be able to split some of the work that synapse does into