Add instructions on how to enable verbose-level logging

Configuration.md

@@ -285,3 +285,10 @@ or with `go tool pprof`:
     go tool pprof -top http://localhost:6060/debug/pprof/heap
 
 For a list of supported profiles go to `http://localhost:6060/debug/pprof/`.
+
+Alternatively, you may want to simply download the file and analyze it later:
+
+```
+wget http://localhost:6060/debug/pprof/heap
+go tool -http=:8080 heap
+```

FAQ.md

@@ -3,6 +3,7 @@
 ## Questions:
 
 * [Why AdGuard Home doesn't block ads?](#doesntblock)
+* [How to configure AdGuard Home to write verbose-level logs](#verboselog)
 * [After installing AdGuard Home, how to change dashboard interface's address?](#webaddr)
 * [How to set up AdGuard Home as default DNS server?](#defaultdns)
 * [How to configure AdGuard Home to run together with pixelsrv-tls?](#pixelsrv)
@@ -53,6 +54,18 @@ Now that you are sure that your device uses AdGuard Home as default DNS server,
 
 
 
+### <a href="#verboselog" id="verboselog">How to configure AdGuard Home to write verbose-level logs?</a>
+
+To troubleshoot a complicated issue, it is often needed to enable verbose-level logging in AdGuard Home. Here's how it should be done:
+
+1. Stop AdGuard Home
+2. Configure AdGuard Home to collect logs. In order to do that, edit `AdGuardHome.yaml`:
+    * Set path to the log file in `log_file`
+    * Set `verbose` to `True`
+3. Restart AdGuard Home and reproduce the issue
+
+
+
 ### <a href="#webaddr" id="webaddr">After installing AdGuard Home, how to change dashboard interface's address?</a>
 
 1. Open `AdGuardHome.yaml` in the text editor