 Hello! In this video I will demonstrate how to enable debug-level logging for OpenShift sandbox containers. At runtime, multiple Cata and Virtualization components are running under the hood, such as Cata Runtime, Cata Agent, QMU, and Virtual FSD. By default, most of these are printing limited amount of log types, mostly error and warning logs. And here we will learn how to enhance logging and print also debug-level logs. Here we have a standard 6-node OpenShift cluster with pre-installed OpenShift sandbox containers that was installed using the operator on the worker nodes. Hence, we can see we already have the Cata Runtime class, which is used by the OpenShift sandbox container. Currently, in order to set OpenShift sandbox container components to print their logs at debug level, we should set also Cryo's log-level to debug. In order to do that, we will use the following container runtime config custom resource, which allows you to customize container runtime configuration, and in this case we will change the configuration of the runtime log-level to debug on each of the worker nodes using machine config pull selector. Let's apply the custom resource. In this case, Cryo is runtime, and changing its configuration restarts the Cryo daemon. Hence, it may take a couple of minutes. We will watch the worker nodes machine config pull and skip that in the video. All nodes are updated. Now, all worker nodes cryo instances as debug-log-level set. From now on, each deployed sandbox workload allows the Cata components running it to print their logs at debug level. Note that the new configuration will be applied only on newly created sandbox workloads. Let's apply some sandbox workloads. Here we have the following configuration, which describes a simple Fedora pod with a runtime class of Cata, which does nothing but sleep. Let's apply it. We can see the pod is already running within a sandbox environment using Cata. Most of the logs printed by the Cata components are printed to the journal log under the Cata identifier. One way to get those is using the OCADM node logs command of OC client. The workload is running on the following node, and let's grab for the Cata identifier. As you can see, it is not a very convenient way to get the logs. Another option would be to get into the node running the workload and try to fetch the logs there. Let's log in into the node running the workload, use the journal ctr command with the Cata identifier to get the logs. You can see we have debug logs, inf logs and other logs. When logs should be collected for support purposes, we would encourage you to simply use and run the massgather tool, which will collect the emitted mentioned logs in addition to many other OpenShift sandbox container logs, the operator logs and other logs, files and useful information. In order to do that, please refer to the OpenShift sandbox container documentation. However, the command looks as follows. Now the massgather tool is running and collects logs into single directory, which can be collected and sent to the support team. Thank you for watching.