What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general.

Learn more

PRTG Network Monitor

Intuitive to Use. Easy to manage.
More than 500,000 users rely on Paessler PRTG every day. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free Download

Top Tags

View all Tags

What are the bandwidth requirements for running a cluster?



Do you have guidelines or averages of bandwidth requirements for clustering? For example, an average of 10kbps per 1,000 sensors?

basics clustering prtg traffic

Created on Aug 26, 2010 10:28:41 AM by  Torsten Lindner [Paessler Support]

Last change on Mar 6, 2020 10:56:42 AM by  Brandy Greger [Paessler Support]

3 Replies

Accepted Answer



This article applies as of PRTG 22

Bandwidth usage in a cluster

  • A cluster only transfers changes. If all sensors are up and running, and no objects are being edited, no data is transferred between the cluster nodes.
  • There is a Keep alive message from each cluster node every 10 seconds, which does not scale with the sensor count, however.
  • On startup or if the cluster nodes are out of sync, there can be a transfer spike when the entire configuration is sent to the other cluster nodes (in a compressed form). You can have a look at the size of your non-compressed configuration file, but as this varies from user to user, it is impossible to name an exact number here.
  • If sensors change to the Up or Down status, the status is broadcast to all other cluster nodes. The traffic caused by this depends on the number of cluster nodes.
  • If the PRTG core server on one of the cluster nodes is updated, the setup file (about 36 MB) is transferred to the other cluster nodes to update them automatically.
  • When the reviewing of monitoring data includes different cluster nodes, the required data (states, graphs, tables) is transferred from the other cluster nodes to the cluster node you are logged in to. Graphs in particular for which All cluster nodes was selected can cause traffic peaks. This affects reports with an All cluster nodes setting, too.
  • In a cluster, every cluster node independently monitors the devices added to the cluster probe. Each of these devices sends monitoring data to every single cluster node. Depending on the number of cluster nodes used, this causes extra traffic.
    Note: Especially when many WMI sensors are used, this can lead to extended traffic on the hosts.

Created on Aug 26, 2010 10:32:11 AM by  Torsten Lindner [Paessler Support]

Last change on Jun 15, 2022 12:07:51 PM by  Brandy Greger [Paessler Support]



What impact should we expect to see in a two node clustered setup on our monitored devices. Are we doubling the amount of SNMP operations that devices must performed, because they are being checked by each clustered node? What considerations has Paessler made for this?

Thanks! JZ

Created on Jul 31, 2014 10:23:36 PM



Yes, when running a cluster configuration, the SNMP queries are performed by both servers thus doubling the amount of SNMP traffic but this traffic is rather negligible and will only occur for those sensors which are underneath the Cluster Probe.

Created on Aug 1, 2014 12:29:07 PM by  Greg Campion [Paessler Support]

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.