What do I have to take into account when planning a large installation of PRTG Network Monitor?
Created on Oct 13, 2011 10:21:36 AM by
Last change on Oct 13, 2011 10:36:11 AM by
2 Replies
Accepted Answer
Planning Large Installations of PRTG Network Monitor
The maximum number of sensors you can monitor with one installation of PRTG mainly depends on the monitoring technology and the monitoring intervals you use:
- SNMP V1/V2, PING, PORT, and HTTP are the recommended sensor types for scenarios with thousands of sensors. With these technologies up to 20,000 sensors are possible.
- For SNMP V3 you will be able to monitor between 60 and 6,000 SNMP V3 sensors with an interval of 60 seconds (depending on request times in your network).
- For WMI monitoring try to keep the number of WMI sensors per probe below 120 sensors (with 60s interval) or 600 sensors (with 300s interval).
- For NetFlow (or sFlow, jFlow) monitoring the maximum number of sensors depends on the traffic pattern, the number of Flow packets per second received by the PRTG Probe, as well as the performance of the probe system (see Site Planner Tool).
- Packet Sniffing creates the highest CPU load on the probe system. This technology is only recommended for monitoring of low traffic connections (<50 Mbit/s steady stream). When traffic is often over 10 Mbit/s a dedicated remote probe should be used.
- VMware monitoring is limited to about 20 sensors at a 60 seconds monitoring interval, or 100 sensors at a 5 minutes interval. These limitations issue from the VMware platform. A registry hack is available to boost this to 150 sensors at a 5 minutes interval (this will require a change in the ESX/vCenter configuration).
To overcome any limitations mentioned above you should distribute the sensors over two remote probes or more.
A stand-alone installation of PRTG can reliably monitor up to 20,000 sensors per installation. For high-speed operation of the web interface (page times below 500ms) we recommend to stay below 10,000-12,000 sensors per installation. For clusters we recommend to stay below 10,000 sensors per cluster.
As a rule of thumb you should not experience any performance issues for installations up to 5.000 sensors in most situations. In the blog article "Page Load Times of PRTG for Large Installations" we have published web page load times for larger installations on selected servers (conclusions also apply to PRTG 9).
For more detailed information please use the Site Planner Tool to plan large installations.
See Also
Created on Oct 13, 2011 10:35:23 AM by
Last change on Apr 3, 2012 2:20:27 PM by
I'd like to add to this comment that it is possible to use more than 120 sensors for WMI. I think our current setup is approximately running a total of 1200 sensors (60 sec interval) with about 250 wmi sensors and we will be adding more of them.
We are however running this single server install on a dual xeon x5660 @ 2.6ghz 12 GB ram machine with a 1gb FBWC raid controler.
In this setup I have 24 cpu's according to task manager. CPU usage is light as well as memory usage.
I don't have jFlow working yet (due to a limitation on the SRX 240 not being able to send out jFlow on reth interfaces) so my main sensors are ping, snmp (v2) and WMI.
This is all local Lan so al latencies are <10ms and I have not had any performance issues. the troubles I've had with WMI are usually due to the fact that we have a lot of win2k8 (non r2) servers which pretty much hate WMI altogether.
Created on Oct 13, 2011 2:52:30 PM by
Last change on Oct 13, 2011 3:05:02 PM by
Please log in or register to enter your reply.
Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.
Add comment