PRTG System Requirements

We recommend that you run the PRTG core server as well as all remote probes

directly on x64 PC/server hardware (not older than 2 years)

on Windows Server 2012 R2 having .NET Framework 4.5 or later installed.

There are many parameters that influence the performance and stability of PRTG, but for the vast majority of PRTG users the following sizing recommendations for the hardware of the PRTG server work fine.

Sensors
per Core Server

License

Recommended Core Server Hardware

Disk Space
(1 year data retention)

User Accounts

Remote Probes

Virtualization

PRTG Cluster

up to 1,000 sensors
(~ 100 devices)

PRTG 1000

2 CPU Cores, 3 GB RAM

250 GB

< 30

< 30

1,000 – 2,500 sensors
(~ 250 devices)

PRTG 2500

3 CPU Cores, 5 GB RAM

500 GB

< 30

< 30

2,500 – 5,000 sensors
(~ 500 devices)

PRTG 5000

5 CPU Cores, 8 GB RAM

1 TB

< 20

< 30

5,000 – 10,000 sensors
(~ 1,000 devices)

PRTG XL1

8 CPU Cores, 16 GB RAM

2 TB

< 10

< 30

More than 10,000 sensors

We recommend that you set up additional PRTG core server installations and contact your presales team.

PRTG System Requirements

PERFORMANCE CONSIDERATIONS

Most PRTG installations will never run into performance issues, but please note the following points that can affect performance:

• As a “Rule of thumb” we can say: Typical PRTG installations almost never run into performance issues when they stay under 5,000 sensors, under 30 remote probes, and under 30 user accounts. If your scenario is listed above go ahead and install PRTG.
• Please use a physical machine. Yes, really! There are several reasons why we recommend that you run PRTG (core server and remote probes) on real hardware, especially for thousands of sensors. Each sensor request will have to go through many virtualization layers, which costs performance and makes measurements less exact. In our experience, a physical machine simply works best for a thousand sensors and more. Our recommendation to use real hardware
is valid for the PRTG core server and for remote probes. If you must run PRTG on a virtual machine, please stay below 5,000 sensors per virtual machine and consider running several PRTG core server instances instead.
• Halfed performance for each additional cluster node. In a PRTG failover cluster, the monitoring load doubles with each cluster node. In a single failover cluster, please divide our recommended numbers from above in half. We recommend a single failover setup if you need fail-safe monitoring. This consists of two PRTG core servers, each working as a cluster node.
• When you use more than 5,000 sensors you should use 5 minutes intervals (instead of 1 minute) or longer.
• Some sensor types create much more load than others. For example, Ping and SNMP sensors create much less load than complex sensors like xFlow sensors, VMware sensors, Sensor Factory sensors, WMI sensors, or Syslog/Trap receiver sensors, to name just a few examples.
• We recommend that you stay below 30 active user accounts for each PRTG core server. You can work well with more users if these do not all use the UI at the same time (including public dashboards).
• Try to keep the usage of the following features down: Many quickly refreshed dashboards (“Maps”), frequent generation of huge sensor reports, heavy usage of packet sniffing, factory sensors and toplists, frequent automatically scheduled auto-discoveries for large network segments, constant queries of monitoring data via the API, among others.
• Load balancing is possible using remote probes: to distribute load, you can set up multiple probes on different computers. For details, see section Remote Probes and Multiple Probes in the PRTG user manual and watch the video tutorial Distributed Monitoring with PRTG.

STABILITY CONSIDERATIONS

Most PRTG installations will never run into stability issues, but please note the following points that can affect the stability of PRTG:
• Remote probes require a stable network connection between the PRTG core server and the remote probe. Unstable connections, for example via 3G or via satellite, may work but we have seen situations where stable monitoring was not possible.
• Our general recommendation is to stay below 30 remote probes on one PRTG core server. PRTG still scales well up to 60 probes as long as you have less than 100 sensors per probe.
• An internet connection is required for license activation (via HTTP or email).
• The quality of your network also plays an important role. When monitoring via UDP, for example, a high packet loss rate can lead to frequent timeouts. Remote probes that connect via unstable (WAN) connections can lead to delays as well.

The following browsers are officially supported for the web browser based primary user interface of PRTG (in order of performance and reliability) at screen resolution of 1024×768 pixels (more recommended):
• Google Chrome 59 or later (recommended)
• Mozilla Firefox 54 or later
• Microsoft Internet Explorer 11
• Other and older browsers might not have full functionality.

PRTG Windows App (Enterprise Console)

The PRTG Enterprise Console app runs under all supported Windows versions (see the list above) at screen resolutions of 1024×768 pixels or more.

Mobile Apps

We provide free apps for Android and iOS devices. Please see Mobile Apps for smartphones and
tablets and the corresponding app pages for detailed system requirements.

REQUIREMENTS FOR MONITORED DEVICES

• SNMP monitoring: The monitored device(s) must be equipped with SNMP Version 1, 2c, or 3 (an SNMP-compatible software must be installed on the device). SNMP must be enabled on the device and the machine running PRTG must be allowed to access to the SNMP interface. For details, please see PRTG Manual: Monitoring via SNMP
• Windows/WMI monitoring: To use WMI (Windows Management Instrumentation) monitoring, you need a Windows network. Host PC and client PCs with Windows OS as given above are officially supported. Please do not use Windows Vista or Windows Server 2008 on host PCs for WMI monitoring, both have WMI performance issues.