1
0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 12:46:18 +01:00
Files
openshift-docs/modules/virt-configuring-pod-log-verbosity.adoc
2026-01-20 17:24:19 +00:00

46 lines
1.3 KiB
Plaintext
Raw Permalink Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
// Module included in the following assemblies:
//
// * virt/support/virt-troubleshooting.adoc
:_mod-docs-content-type: PROCEDURE
[id="virt-configuring-pod-log-verbosity_{context}"]
= Configuring {VirtProductName} pod log verbosity
[role="_abstract"]
You can configure the verbosity level of {VirtProductName} pod logs by editing the `HyperConverged` custom resource (CR).
.Prerequisites
* You have installed the {oc-first}.
.Procedure
. To set log verbosity for specific components, open the `HyperConverged` CR in your default text editor by running the following command:
+
[source,terminal,subs="attributes+"]
----
$ oc edit hyperconverged kubevirt-hyperconverged -n {CNVNamespace}
----
. Set the log level for one or more components by editing the `spec.logVerbosityConfig` stanza. For example:
+
[source,yaml]
----
apiVersion: hco.kubevirt.io/v1beta1
kind: HyperConverged
metadata:
name: kubevirt-hyperconverged
spec:
logVerbosityConfig:
kubevirt:
virtAPI: 5
virtController: 4
virtHandler: 3
virtLauncher: 2
virtOperator: 6
----
+
The log verbosity value must be an integer in the range `19`, where a higher number indicates a more detailed log. In this example, the `virtAPI` component logs are exposed if their priority level is `5` or higher.
. Apply your changes by saving and exiting the editor.