CHAPTER 23

Monitoring Your SimpleVM Host

5 sections · 9 min read · SimpleVM 10.1

Monitoring a SimpleVM host means watching the host and its virtual machines closely enough to notice when something is drifting away from normal — ideally before it becomes an outage. Every page you need is in the web console, and the pages are most useful in a consistent order: start at the host overview for a whole-host picture, narrow to an individual virtual machine, confirm storage and networking, check update and reboot status, and reach for the web terminal only when the console does not show enough detail.

Monitoring is also a habit, not only an emergency response. Reviewing the same pages on a normal day builds a baseline — what CPU, memory, storage, and network activity look like when nothing is wrong — so that the day something is wrong, the difference stands out. That same baseline supports capacity planning: it tells you when the host is approaching the limit of the workloads it can carry. Where Chapter 7, Understanding the Dashboard and Host Overview explains what each dashboard panel means, this chapter turns those panels into a repeatable routine and points you to the specific page to open when an indicator looks wrong.

23.1 Monitoring Overview

Overview

SimpleVM monitoring begins in the web console. The host overview, the virtual machine detail pages, the storage pages, the networking pages, the firewall view, the software updates page, and the web terminal together provide the first layer of visibility into the environment. The single most useful habit is to follow the same order every time, working from the whole host down to the specific resource — that way you build a baseline and you never skip the page that would have shown the problem first.

The monitoring workflow

A healthy monitoring routine usually follows this order:

Review the host Overview for health, CPU, memory, storage, and system information.
Review individual virtual machines that are slow, stopped, or showing high usage.
Review storage capacity, disk activity, and storage pool status.
Review network interfaces, firewall state, and virtual networks.
Check software update and reboot status (see Chapter 18, Software Updates).
Use the web terminal or command line only when the web console does not provide enough detail (see Chapter 19, Host Administration Tools, and Section 19.4, Web Terminal Overview; broader command-line reference is in Chapter 26, Advanced Administration and Command-Line Reference).

23.2 Host Resource Monitoring

Overview

Host resource monitoring answers one question: does the host have enough CPU, memory, storage, and network capacity for the virtual machines it is running? Begin at the host Overview before opening individual resource pages, because the overview shows the four resources together and points you to the one that needs attention.

Before you begin

You need administrative access to the web console (see Chapter 6, Accessing the SimpleVM Management Interface, and Section 6.5, Sign In with Administrative Access).
Knowing the host's normal CPU, memory, and storage baseline makes an abnormal reading easier to recognize. If you do not have a baseline yet, this routine is how you build one.

Procedure

Sign in to the SimpleVM management interface.
Open the host Overview page.
In the Health panel, review update status and the most recent successful login.
In the Usage panel, review CPU (shown as a percentage of total CPUs) and memory (used of total). Select View metrics and history to see recent trends rather than a single instant.
Confirm that available storage is not approaching capacity.
Review System information and the Configuration summary for anything unexpected.
If a resource looks abnormal, open the related page for detail rather than acting from the overview alone.

What to look for

Indicator	What it can mean	Suggested next step
Sustained high CPU usage	The host or one or more VMs may be CPU-bound.	Review per-VM CPU usage (Section 23.3) and recent workload changes; tune in Chapter 24
Sustained high memory usage	VMs may be overcommitted, a guest may be using more memory than expected, or the host may need more RAM.	Review VM memory allocations and guest behavior (Section 23.3).
Low available storage	Storage pools, ISOs, logs, snapshots, or VM disks may be consuming space.	Review host storage and storage pools (Section 23.4) before creating new VMs or snapshots.
Unexpected network activity	A VM, backup job, migration, update task, or external client may be generating traffic.	Review host and virtual networking (Section 23.5) and VM interfaces.

Verification

The host Overview should give you a clear first-pass picture of host health and resource usage. If it does not explain the issue, continue to the monitoring section for the affected resource. For deeper interpretation of these same panels, see Section 7.1, Host Overview Page and Section 7.4, CPU, Memory, Storage, and Network Status. Because this procedure only reads state, there is nothing to revert.

23.3 VM Resource Monitoring

Overview

VM resource monitoring shows whether an individual virtual machine is using the CPU, memory, disk, and network resources assigned to it. Use this view when a guest feels slow, fails to boot, becomes unresponsive, or appears to be affecting other VMs. Everything starts from the VM's detail page.

Procedure

Open Virtual machines.
Select the virtual machine you want to review.
Review the VM State, open the graphical Console, and review the visible CPU and memory Usage (opening a console is covered in Section 8.8, Opening a VM Console).
Open the VM Disks, Network interfaces, Host devices, and Snapshots sections as needed.
Compare current behavior with recent changes — guest updates, application changes, added disks, snapshot activity, or network changes.

Figure 23-2. A virtual machine detail page showing the VM Overview, Usage, and the graphical Console. This is where per-VM resource monitoring begins. — **Figure 23-2.** A virtual machine detail page showing the VM **Overview**, **Usage****, and the graphical** **Console***. This is where per-VM resource monitoring begins.*

Figure 23-3. The same VM's Disks, Network interfaces, Host devices, and Snapshots sections — used to confirm that the VM's disks, connectivity, and snapshot state match what you expect. — **Figure 23-3.** The same VM's **Disks**, **Network interfaces**, **Host devices****, and** **Snapshots** **sections — used to confirm that the VM***'s disks, connectivity, and snapshot state match what you expect.*

What to look for

Check	Why it matters
VM power state	Confirms whether the VM is running, shut off, paused, or in another state.
Console response	Shows whether the guest is booting, waiting for input, or displaying an error.
CPU and memory activity	Helps identify workload pressure or a VM that is under-sized for its current role.
Disk configuration	Confirms that expected disks are attached and visible (see Chapter 9, Managing VM Disks).
Network interfaces	Confirms attachment to the expected virtual network or bridge (see Chapter 10, Managing VM Network Interfaces).
Snapshots	Shows whether snapshot usage may affect storage capacity or recovery expectations (see Chapter 11, VM Snapshots).

Verification

The VM detail page should explain whether the guest is running and using resources as expected. If the VM looks healthy but the symptom persists, correlate it with host-wide resource pressure (Section 23.2) and storage activity (Section 23.4). This procedure only reads state, so there is nothing to revert.

23.4 Storage Monitoring

Overview

Storage problems can affect VM performance, VM creation, snapshots, migration, and backups, so storage deserves regular attention rather than only emergency checks. Monitor storage at two layers. Storage pools show where VM images and ISO files live; the host Storage page shows the underlying disks, partitions, logical volumes, and read/write activity that those pools depend on.

Procedure

Open the Storage pools page (reached from Virtual machines).
Confirm that the required pools — for example, the default VM image pool and the ISO pool — are active.
Review used and available capacity for each pool.
Open the host Storage page.
Review the read/write activity graphs and the list of disks, partitions, and logical volumes.
Investigate any device that appears missing, full, inactive, or unusually busy.

Figure 23-4. The Storage pools page showing the default VM image pool and the ISO pool, with their paths and state. Storage pools are covered in Chapter 12, Managing Storage Pools. — **Figure 23-4.** The **Storage pools** **page showing the default VM image pool and the ISO pool, with their paths and state. Storage pools are covered in** **Chapter 12, Managing Storage Pools**.

Figure 23-5. The host Storage page showing read/write activity graphs and the underlying disks, partitions, and logical volumes. Host storage is covered in Chapter 13, Managing Host Storage. — **Figure 23-5.** The host **Storage** **page showing read/write activity graphs and the underlying disks, partitions, and logical volumes. Host storage is covered in** **Chapter 13, Managing Host Storage**.

What to look for

Symptom	Possible cause	First check
VM creation fails	The target pool may be inactive or full.	Confirm the pool is active and has capacity (Chapter 12).
VM boots slowly	The underlying disk may be busy, or the guest may be waiting on I/O.	Check host storage read/write activity (Section 13.4, Storage Performance Graphs) and guest activity.
Snapshot fails	The pool may not have enough free space.	Review pool capacity before retrying (Chapter 11).
ISO upload fails	ISO storage may be full, or permissions may need checking.	Review ISO pool capacity and File Browser behavior.

Verification

After this routine you should know which pools are active, how much capacity remains, and whether host storage is healthy and not unusually busy. If capacity or activity looks wrong, treat the follow-up as a change — plan it, back up first, and apply it under the relevant storage chapter. This procedure itself only reads state, so there is nothing to revert.

23.5 Network Monitoring

Overview

Network monitoring helps you decide where a connectivity problem lives — inside a VM, inside a virtual network, on the SimpleVM host, or out on the physical network. Review host networking and virtual networks together, because VM connectivity depends on both layers at once.

Procedure

Open the host Networking page.
Review transmit and receive activity on the graphs.
Confirm that the expected physical interfaces are present and active.
Review firewall status and related networking information (see Chapter 16, Firewall and Security Settings).
Open the Networks page.
Confirm that each VM is connected to the expected virtual network.
Check whether the virtual network's DHCP range, static host entries, and forwarding mode match the intended design.

Figure 23-6. The host Networking page showing transmit and receive graphs, firewall status, and the physical interfaces. Host networking is covered in Chapter 15, Managing Host Networking. — **Figure 23-6.** The host **Networking** **page showing transmit and receive graphs, firewall status, and the physical interfaces. Host networking is covered in** **Chapter 15, Managing Host Networking**.

Figure 23-7. The Networks page showing the default NAT virtual network, its DHCP range, and static host entries. Virtual networks are covered in Chapter 14, Managing Virtual Networks. — **Figure 23-7.** The **Networks** **page showing the default NAT virtual network, its DHCP range, and static host entries. Virtual networks are covered in** **Chapter 14, Managing Virtual Networks**.

What to look for

Question	Where to check first
Can the SimpleVM host reach the network?	Host Networking page, and gateway/DNS settings (Chapter 15).
Can the VM reach the host?	VM network interface and virtual network attachment (Chapter 10, Chapter 14).
Can the VM reach other systems?	Virtual network mode, bridge/NAT configuration, firewall rules, and the physical network path.
Did the problem start after a firewall or interface change?	Firewall page, host Networking page, and recent configuration changes.

Verification

After reviewing both layers, you should be able to place the problem at the host, the virtual network, the VM interface, or the physical network beyond SimpleVM. If host and virtual networking both look correct but a VM still cannot connect, move to Chapter 25, Troubleshooting (see Section 25.6, Network Issues). This procedure only reads state, so there is nothing to revert.