<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Monitoring on OpenShift Virtualization Training</title><link>/docs/monitoring/</link><description>Recent content in Monitoring on OpenShift Virtualization Training</description><generator>Hugo</generator><language>en</language><atom:link href="/docs/monitoring/index.xml" rel="self" type="application/rss+xml"/><item><title>Guest agent</title><link>/docs/monitoring/guest-agent/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/docs/monitoring/guest-agent/</guid><description>&lt;p>In many of the available cloud images, the &lt;code>qemu-guest-agent&lt;/code> package is already installed. If it&amp;rsquo;s not preinstalled you can use one of the previously learned concepts to install the package.&lt;/p>
&lt;h2 id="task-811-start-a-virtual-machine-and-explore-guest-agent-information">Task 8.1.1: Start a virtual machine and explore guest agent information&lt;/h2>
&lt;p>In this lab we are going to reuse the virtual machine we created in the &lt;a href="/docs/initialize-vms-with-startup-scripts/cloud-init/">4.2. Cloud-init&lt;/a> lab.&lt;/p>
&lt;p>Start the &lt;code>cloud-init&lt;/code> virtual machine using the following command:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>virtctl start lab04-cloudinit --namespace lab-&amp;lt;username&amp;gt;
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>The presence of the guest agent in the virtual machine is indicated by a condition in the VirtualMachineInstance&amp;rsquo;s status. This condition shows that the guest agent is connected and ready for use.&lt;/p></description></item><item><title>Readiness and liveness probes</title><link>/docs/monitoring/probes/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/docs/monitoring/probes/</guid><description>&lt;p>Liveness and readiness probes can be configured for VirtualMachineInstances similarly to how they are defined for containers. You can find more information about these probes &lt;a href="https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/" target="_blank" rel="noopener">in Kubernetes&amp;rsquo; documentation&lt;/a>
.&lt;/p>
&lt;p>Liveness probes will stop the VirtualMachineInstance if they fail, allowing higher-level controllers, such as VirtualMachine or VirtualMachineInstanceReplicaSet, to create new instances that should be responsive.&lt;/p>
&lt;p>Readiness probes signal to Services and Endpoints whether the VirtualMachineInstance is ready to handle traffic. If these probes fail, the VirtualMachineInstance will be removed from the list of Endpoints backing the Service until the probe recovers.&lt;/p></description></item><item><title>Prometheus monitoring</title><link>/docs/monitoring/prometheus-monitoring/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/docs/monitoring/prometheus-monitoring/</guid><description>&lt;p>Prometheus is an open-source monitoring and alerting toolkit designed for reliability and scalability. It collects real-time metrics from services and systems, stores them in a time-series database, and provides powerful querying capabilities. Prometheus operates with a pull-based model, scraping metrics from endpoints at regular intervals. It supports multi-dimensional data through labels, enabling flexible queries and insights. Paired with tools like Grafana for visualization, Prometheus is widely used for monitoring cloud-native applications, infrastructure, and system performance, with built-in alerting to notify users of potential issues.&lt;/p></description></item><item><title>Prometheus Node Exporter</title><link>/docs/monitoring/node-exporter/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/docs/monitoring/node-exporter/</guid><description>&lt;p>The Prometheus Node Exporter is a key component used for collecting operating system metrics from Linux and Windows systems. It exposes a wide range of system-level metrics that Prometheus can scrape, making it useful for monitoring the health and performance of physical and virtual machines.&lt;/p>
&lt;p>Some of the key metrics collected by Node Exporter include:&lt;/p>
&lt;ul>
&lt;li>CPU usage: Tracks how much CPU time is being used by user and system processes&lt;/li>
&lt;li>Memory usage: Monitors free and used memory, swap space, and buffer/cache utilization&lt;/li>
&lt;li>Disk I/O: Provides insights into disk read/write operations and storage usage&lt;/li>
&lt;li>Network statistics: Captures metrics on data sent and received over network interfaces&lt;/li>
&lt;li>File system usage: Monitors available and used space on file systems&lt;/li>
&lt;/ul>
&lt;p>Node Exporter runs as a lightweight daemon on each node and is easy to install and configure. It works out of the box, exposing most common system metrics through the &lt;code>/metrics&lt;/code> endpoint, but can also be extended with additional collectors to gather more specialized data. These metrics can be visualized through tools like Grafana, helping administrators monitor and troubleshoot infrastructure performance.&lt;/p></description></item></channel></rss>