diff --git a/developer_guides/debugability/logger/index.rst b/developer_guides/debugability/logger/index.rst
index db19d11f..68ac83a2 100644
--- a/developer_guides/debugability/logger/index.rst
+++ b/developer_guides/debugability/logger/index.rst
@@ -190,6 +190,34 @@ A similar example may be prepared for components on a particular pipeline:
 
    sof-loggerr -l ldc_file -t -Fc=* -Fv=*1.*
 
+.. note:: 
+  To track verbose message use firmware build with selected "Trace verbose"
+  option under "Trace" menu.
+
+Active trace filters are stored in firmware runtime memory, so after firmware
+restart (eg. after power gating in sleep mode) filters settings will be reset.
+Consider disabling power gating during your debug session.
+It may be done by:
+
+.. code:: bash
+
+  sudo su
+  echo on >/sys/devices/pci0000\:00/0000\:$(lspci -nn | grep "audio contoller" | awk '{print $1;}')/power/control
+
+.. note::
+  Current device power status may be read by this command:
+  
+  .. code:: bash
+  
+    cat /sys/devices/pci0000\:00/0000\:$(lspci -nn | grep "audio controller" | awk '{print $1;}')/power/runtime_status
+
+Logger trace filtration affect only traces sent after filter setup, so traces
+already stored on kernel side will not be affected.
+
+Filters are setup incrementally, so when logger will be run-up twice with
+different settings, then filters from first run will not be restored to default
+state but can be replaced by new one.
+To reset filters to default state, firmware reset is needed.
 
 Detailed description
 --------------------