kbase: debuglogs: Extract client library logging setup

Signed-off-by: Peter Krempa <pkrempa@redhat.com>
Reviewed-by: Erik Skultety <eskultet@redhat.com>

diff --git a/docs/kbase/debuglogs.rst b/docs/kbase/debuglogs.rst
index 652c4359f214242d0fb904d3361248e6d4daa7fc..ad0e8ba5fc6b707564994f1e376b6d04ed96d03c 100644 (file)
--- a/docs/kbase/debuglogs.rst
+++ b/docs/kbase/debuglogs.rst
@@ -89,7 +89,7 @@ configuring your filters is to start with the `Example filter settings`_.
 The rule of thumb here is to have more logs rather than less and miss something
 important.
 
-How to turn on debug logs for libvirt
+Libvirt daemons logging configuration
 =====================================
 
 Persistent setting
@@ -120,14 +120,6 @@ URI <https://libvirt.org/uri.html>`__. For ``qemu:///system``:
 patterns and thus requires more configuration. See
 `Legacy (pre-4.4.0) libvirt daemon logging configuration`_.
 
-In case you want to get the client logs, you need to set this environment
-variable:
-
-::
-
-   export LIBVIRT_LOG_OUTPUTS="1:file:/tmp/libvirt_client.log"
-
-
 However, when you are using the session mode ``qemu:///session`` or you run the
 ``libvirtd`` as unprivileged user you will find configuration file under
 ``$XDG_CONFIG_HOME/libvirt/libvirtd.conf``.
@@ -214,6 +206,19 @@ Or using ``virt-admin``:
    ## LEGACY APPROACH ENUMERATING ALL THE DESIRED MODULES ##
    # virt-admin daemon-log-filters "1:util 1:libvirt 1:storage 1:network 1:nodedev 1:qemu"
 
+Client library logging
+======================
+
+By default the client library doesn't produce any logs and usually usually it's
+not very interesting on its own anyway.
+
+In case you want to get the client logs, logging is controlled via the
+``LIBVIRT_LOG_OUTPUTS`` and ``LIBVIRT_LOG_FILTERS`` environment variables.
+Generally when client logs are needed make sure you don't filter them:
+
+::
+
+   export LIBVIRT_LOG_OUTPUTS="1:file:/tmp/libvirt_client.log"
 
 What to attach?
 ===============