PRTG – P4 How to Monitor Proxmox with PRTG (Basic Monitoring Setup)

Proxmox is widely used for virtualization, but without monitoring, performance issues can go unnoticed.

In this tutorial, you will learn how to Monitor Proxmox with PRTG Network Monitor using a basic setup. This guide is ideal for beginners and system administrators who want a simple and reliable monitoring foundation.

We will configure essential sensors to monitor CPU usage, memory consumption, disk space, network traffic, and system availability. PRTG provides real-time visibility into your Proxmox host and virtual environment.

With proper monitoring in place, you can detect issues early, avoid unexpected downtime, and maintain a stable virtualization platform. This setup works well for home labs and production servers alike.

This video is part of the PRTG Network Monitoring Tutorial Series.

🛠 Step 1: Enable SNMP on Proxmox

To Monitor Proxmox with PRTG, we first need to enable SNMP on the Proxmox host.

On the Proxmox host, run:

Now configure SNMP:

Example of simple and secure configuration in a LAN (delete all content from the paste file):

Allow IP PRTG (or LAN subnet)

Restart SNMP:

At this stage, Proxmox is ready to respond to SNMP requests from PRTG.

🖥 Step 2: Add Proxmox to PRTG

Now we add the Proxmox host to PRTG.

Navigate to:

Devices → Local Probe → Add Device

Enter:

• Device name: Proxmox Host 1

• IP: Proxmox IP

Click Save.

Your Proxmox server is now added as a monitored device.

📡 Step 3: Add the Sensor You Should Use

To properly Monitor Proxmox, we will add several essential sensors.

🔹 1. Ping

→ Check if the host is live

Add Sensor → Ping

This verifies availability and basic network connectivity.

🔹 2. SNMP CPU Load

Add Sensor → SNMP CPU Load

This sensor monitors overall CPU utilization on the Proxmox node.

Monitoring CPU usage is critical to detect overload conditions affecting virtual machines.

🔹 3. SNMP Memory v2

Add Sensor → SNMP Memory

RAM difference between Proxmox node and PRTG:

• Cache / buffer

• PRTG is not considered “available immediately”

Edit PRTG to minimize for accuracy.

Suggested thresholds:

• Lower: warning 10%

• Lower: error 5%

This ensures alerts trigger when available memory becomes critically low.

🔹 4. SNMP Disk Free v2

Add Sensor → SNMP Disk Free

Select disk:

• /

• /var/lib/vz

• local-lvm

Suggested correct thresholds:

For sensor /:

• Lower Warning: < 20% free

• Lower Error: < 10% free

Disk monitoring is extremely important in virtualization environments. When storage fills up, virtual machines may stop unexpectedly.

🔹 5. SNMP Traffic (NIC)

Add Sensor → SNMP Traffic

Select interface:

• vmbr0

• Physical NIC (eno1 / enpXsY)

Monitoring network interfaces helps detect bandwidth saturation or unusual traffic spikes.

📊 Why Monitoring Proxmox Is Critical

When you Monitor Proxmox properly, you gain:

• 📈 Real-time resource visibility

• 🚨 Early detection of overload

• 📊 Historical performance analysis

• 🔔 Instant alerting

• 🛠 Faster troubleshooting

Virtualization environments are resource-sensitive. Without monitoring, small performance issues can escalate quickly.

🛡 Best Practices for Proxmox Monitoring

To improve accuracy and reliability:

• Use SNMP v2c or SNMP v3 securely

• Restrict SNMP community by IP

• Set appropriate scanning intervals

• Monitor both system and network layers

• Regularly review sensor thresholds

Always secure SNMP configuration to avoid exposing system data.

📌 Final Thoughts

Setting up basic monitoring to Monitor Proxmox with PRTG is straightforward yet powerful. With SNMP enabled and essential sensors configured for CPU, memory, disk, and network traffic, you gain full visibility into your virtualization infrastructure.

This foundational setup provides proactive monitoring for both lab and production environments. Once implemented, you can expand further with advanced sensors and deeper VM-level monitoring.

In the next part of this series, we will explore more advanced Proxmox monitoring techniques using PRTG to enhance performance tracking and operational stability.