If your organization is expanding and looking to introduce additional elements and monitors, follow this guide on scalability recommendations. We've outlined the maximum counts and limits for resources and metrics in OpManager to maintain optimal performance. Use the OpManager System Requirements calculator and Disk Space calculator to get an accurate estimate of your system's required specifications.
Listed below are the maximum counts and limits for various elements and monitors in OpManager.
We recommend monitoring up to 10000 interfaces in a single installation. If the count exceeds 10000, it will be efficient to increase the monitoring interval of those interfaces. Adding more interfaces will directly impact the overall performance of the product.
Note:
Without carrying out load-related configuration changes or affecting the network performance, you can install and monitor up to 500 agent-based devices for hassle-free network monitoring.
OpManager restricts the number of elements per group to 2000 to avoid any lapse in the performance of the product. Further elements cannot be added to the group if the limit is reached.
We recommend adding less than 500 elements in a business view for better visualization of devices in the MapView page.
OpManager can monitor a maximum of 2500 access points at once. Regardless of the number of wireless LAN controllers in your inventory, the maximum cumulative number of associated access points that can be monitored, is 2500. In an Enterprise Edition, you can monitor a maximum 2500 access points per probe.
To avoid any hindrance in the performance of the product, OpManager limits the count of VLANs discovered to a maximum of 3,000. New VLANs will not be allowed to be discovered in OpManager post the specified limit.
To avoid any performance degradation in OpManager, the number of traps to be processed per hour is limited to a maximum of 50,000. If this threshold is breached, OpManager stops processing traps for a temporary period.
Based on the monitor type/protocol being used with the performance or availability monitor , these are the maximum advisable number of monitors for a single installation:
| Protocol | Max Number of Monitors Per Installation | Monitoring Interval | Polls/min |
|---|---|---|---|
| SPOLL | 1000 | 5 | 200 |
| SNMP & Interface | 15000 | 15 | 1000 |
| WMI & Application Monitors | 4000 | 15 | 300 |
| CLI | 2500 | 15 | 150 |
| VMware | 10000 | 10 | 1000 |
| HyperV | 5000 | 10 | 500 |
| Xen | 5000 | 10 | 500 |
| Maximum Load (per installation) | 20000 | 10 | 1500 |
Overall, the maximum number of monitors per installation is 20000 including interface monitors. It is also to be noted that adding monitors with more than 100 instances, will indirectly affect the performance of OpManager.
Note:
A Syslog rate of 200 Syslogs per 2 minutes is recommended to avoid any hindrance in the product performance.
If the Netflow processing limit exceeds 1000 flows per second, it will affect OpManager's performance. It is advised to ensure the Netflow processing limit is within the recommended rate.
Please ensure the Firewall log processing limit is under 1000 logs per second to avoid any lapse in the performance of the product.
Monitoring bandwidth
OpManager Enterprise Edition monitors multiple remote sites using OpManager Central and probe servers. The maximum number of devices monitored by OpManager Enterprise Edition, maximum number of probes supported, etc. are discussed below.
| Maximum number of devices monitored | 10,000 |
| Maximum number of interfaces monitored | 50,000 |
For Enterprise Edition with Lite Central enabled
OpManager Enterprise's Lite central option helps you retain the archived data at probe level, helping you optimize performance by reducing the load on Central server's database.
| Maximum number of devices monitored | 30,000 |
| Maximum number of interfaces monitored | 100,000 |
Number of supported probes
For OpManager Enterprise and Enterprise Edition's lite Central option, a maximum of 100 probes will be supported.
Maximum allowable latency
It is important to ensure that the latency between your OpManager's Central server and a connected Probe is within 50 ms (both ways). The Central server can still function at a higher latency but when the latency crosses 100 ms, its performance can be affected.
Maximum number of alerts processed
The Probes send alarm details to the Central and the Central server is capable of processing 1000 alerts per minute, maintaining its peak performance. Please note that the Central is capable of handling more than 1000 alerts per minute as well, but it may have a slight impact in its performance.
If you need to monitor more than the mentioned scalability recommendations, please contact our support team at opmanager-support@manageengine.com.
Thank you for your feedback!
