External/libvirt
1
0
Fork 0
mirror of https://gitlab.com/libvirt/libvirt.git synced 2024-12-22 21:55:25 +00:00
Code Issues Packages Projects Releases Wiki Activity

kbase: debuglogs: Section off the settings for legacy libvirt

Browse Source 
Move out the settings required to pre libvirt-4.4.0 deployments into a
separate section so that the main point is not cluttered by now mostly
irrelevant settings.

Signed-off-by: Peter Krempa <pkrempa@redhat.com>
Reviewed-by: Erik Skultety <eskultet@redhat.com>
This commit is contained in:
Peter Krempa 2022-01-17 12:15:17 +01:00
parent 58d0cf480d
commit 5e38c32e3d
1 changed files with 28 additions and 20 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

48
docs/kbase/debuglogs.rst
View File

@ -33,14 +33,6 @@ URI <https://libvirt.org/uri.html>`__. For ``qemu:///system``:
:: ::
# LEGACY SETTINGS PRIOR LIBVIRT 4.4.0 SEE BELOW! #
log_level = 1
log_filters="1:qemu 3:remote 4:event 3:util.json 3:rpc"
log_outputs="1:file:/var/log/libvirt/libvirtd.log"
::
# PREFERRED SETTINGS AFTER LIBVIRT 4.4.0 #
log_filters="3:remote 4:event 3:util.json 3:rpc 1:*" log_filters="3:remote 4:event 3:util.json 3:rpc 1:*"
log_outputs="1:file:/var/log/libvirt/libvirtd.log" log_outputs="1:file:/var/log/libvirt/libvirtd.log"
@ -51,12 +43,10 @@ URI <https://libvirt.org/uri.html>`__. For ``qemu:///system``:
systemctl restart libvirtd.service systemctl restart libvirtd.service
In the config variables above, we have set logging level to 1 (debug level), set
some filters (to filter out noise), e.g. from rpc only warnings (=level 3) and *Note:* Libvirt prior to the ``libvirt-4.4.0`` release didn't support globbing
above will be reported. The logs are saved into patterns and thus requires more configuration. See
``/var/log/libvirt/libvirtd.log``. Since libvirt **4.4.0** log filters support `Legacy (pre-4.4.0) libvirt daemon logging configuration`_.
shell globbing, therefore the usage of ``log_level`` is considered deprecated in
favour of pure usage of ``log_filters``.
In case you want to get the client logs, you need to set this environment In case you want to get the client logs, you need to set this environment
variable: variable:
@ -91,12 +81,6 @@ own set of filters:
:: ::
## LEGACY APPROACH ENUMERATING ALL THE DESIRED MODULES ##
# virt-admin daemon-log-filters "1:util 1:libvirt 1:storage 1:network 1:nodedev 1:qemu"
::
## CURRENT APPROACH USING SHELL GLOBBING ##
# virt-admin daemon-log-filters "3:remote 4:util.json 4:rpc 1:*" # virt-admin daemon-log-filters "3:remote 4:util.json 4:rpc 1:*"
Analogically, the same procedure can be performed with log outputs: Analogically, the same procedure can be performed with log outputs:
@ -135,6 +119,30 @@ setting which depends on the host configuration, *journald* in our case:
# virt-admin daemon-log-outputs "" # virt-admin daemon-log-outputs ""
Logging outputs: 2:journald Logging outputs: 2:journald
Legacy (pre-4.4.0) libvirt daemon logging configuration
-------------------------------------------------------
Old libvirt versions didn't support globbing (e.g. ``1:*``) to configure
logging, thus it's required to explicitly set logging level to 1 (debug level)
with the ``log_level`` setting and then filter out the noise with a tailored log
``log_filters`` string.
::
# LEGACY SETTINGS PRIOR LIBVIRT 4.4.0
log_level = 1
log_filters="1:qemu 3:remote 4:event 3:util.json 3:rpc"
log_outputs="1:file:/var/log/libvirt/libvirtd.log"
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"
What to attach? What to attach?
=============== ===============