From dc6fa5ac6a3c6008b165c28ce49f4b294c5881f5 Mon Sep 17 00:00:00 2001
From: Joe Mooring <joe.mooring@veriphor.com>
Date: Sat, 15 Jun 2024 11:42:37 -0700
Subject: [PATCH] Document LiveReload debugging

Closes #2625
---
 content/en/troubleshooting/logging.md | 16 ++++++++++++++++
 1 file changed, 16 insertions(+)

diff --git a/content/en/troubleshooting/logging.md b/content/en/troubleshooting/logging.md
index 8879c1846..380389bca 100644
--- a/content/en/troubleshooting/logging.md
+++ b/content/en/troubleshooting/logging.md
@@ -54,3 +54,19 @@ If you do not specify a logging level with the `--logLevel` flag, warnings and e
 You can also use template functions to print warnings or errors to the console. These functions are typically used to report data validation errors, missing files, etc.
 
 {{< list-pages-in-section path=/functions/fmt filter=functions_fmt_logging filterType=include >}}
+
+## LiveReload
+
+To log Hugo's LiveReload requests in your browser, add this query string to the URL when running Hugo's development server:
+
+```text
+debug=LR-verbose
+```
+
+For example:
+
+```text
+http://localhost:1313/?debug=LR-verbose
+```
+
+Then monitor the reload requests in your browser's dev tools console. Make sure the dev tools "preserve log" is enabled.