If your organization is expanding and adding elements and monitors, use these recommendations to keep OpManager performing well. They list the maximum counts and limits for resources and metrics. Use the System Requirements calculator and Disk Space calculator for an accurate estimate of your required specifications.
| Limit | Enterprise |
|---|---|
| Devices | 5,000 per probe |
| Agent devices | 5,000 per probe |
| Access points | 5,000 per probe |
| Interfaces | 15,000 per probe |
| Polls/min (max load) | 5,000 per installation |
| SNMP traps | 50,000 per hour |
| Total devices (Central) | 10,000 on Central, or 30,000 with Lite Central |
Note: The limits specified above are applicable to OpManager Enterprise Edition versions 129200 and above. For recommendations applicable to versions 128398 to 129199, click here.
| Element | Limit | Notes |
|---|---|---|
| Devices | 5,000 | Maintain the recommended device count, including agent devices and access points, per probe for optimal monitoring performance. |
| Agent devices | 5,000 | Maintain the recommended agent count to ensure seamless agent deployment and efficient monitoring. |
| Access points | 5,000 | Maintain the recommended access point count across all wireless LAN controllers for efficient discovery and monitoring.. |
| Interfaces | 15,000 | Maintain the recommended interface count per probe. For additional interfaces beyond the recommended count, increase the monitoring interval to ensure optimal monitoring performance. |
| VLANs | 3,000 | Maintain the recommended VLAN count for efficient discovery and monitoring |
| Elements per group | 5,000 | Maintain the recommended group size for efficient element organization and management. |
| Elements per business view | < 500 | Maintain the recommended element count for optimal visualization on the MapView page. |
Based on the protocol used by the performance and availability the maximum advisable number of monitors for a single probe monitoring up to 5,000 devices is given below.
| Protocol | Interval | Polls per minute |
|---|---|---|
| Availability | 5 min | 1,000* |
| SNMP and interface | 15 min | 4,000 |
| WMI and application | 15 min | 1,000** |
| CLI | 15 min | 300 |
| VMware | 10 min | 2,000 |
| Xen | 10 min | 1,000 |
| Data ingestion | 5 min | 300 |
*Availability: A rate of 1,000 polls per minute is only recommended when using the "Windows Native API based Availability Monitoring (ICMP dll)" protocol for availability monitoring. For other protocols, a rate of 300 polls per minute is recommended.
**WMI and application monitors: A polling rate of up to 400 polls per minute is supported for DCOM, and 600 polls per minute for WinRM, subject to a combined limit of 1,000 polls per minute. These limits apply to version 129135 and later. For earlier versions, a total of 400 polls per minute is recommended.
Maximum load (per installation): To ensure optimal performance, it is recommended to maintain a combined polling rate of up to 5,000 polls per minute per probe across all protocols.
| Type | Processing limit | What to know |
|---|---|---|
| Alert processing limit | 1,000 alerts per minute | Maintain the recommended alert processing rate for optimal performance across Probes and the Central server. |
| Trap processing limit | 50,000 per hour | Maintain the recommended trap processing rate to ensure uninterrupted monitoring. |
| Syslog processing limit | 100 per minute | Maintain the recommended Syslog processing rate to ensure uninterrupted monitoring. |
| NetFlow processing limit | 1,000 flows per second | Maintain the recommended NetFlow processing rate for efficient flow analysis and monitoring. |
| Firewall logs processing limit | Under 1,000 logs per second | Maintain the recommended firewall log processing rate for efficient log monitoring |
| Limit | Standard/Professional |
|---|---|
| Devices | 1,000 per installation |
| Agent devices | 1000 per installation |
| Access points* | 1000 in total |
| Interfaces | 10,000 per installation |
| Polls/min (max load) | 1,500 per installation |
| SNMP traps | 30,000 per hour |
Access points*: To extend access point monitoring beyond the recommended limit, contact the support team at opmanager-support@manageengine.com
| Element | Limit | Notes |
|---|---|---|
| Devices | 1,000 | Maintain the recommended device count, including agent devices and access points, for optimal monitoring performance. |
| Agent devices | 1,000 | Maintain the recommended agent count to ensure seamless agent deployment and efficient monitoring. |
| Access points | 1,000 | Maintain the recommended access point count across all wireless LAN controllers for efficient discovery and monitoring. |
| Interfaces | 10,000 | Maintain the recommended interface count. For additional interfaces beyond the recommended count, increase the monitoring interval to ensure optimal monitoring performance. |
| VLANs | 3,000 | Maintain the recommended VLAN count for efficient discovery and monitoring |
| Elements per group | 5,000 | Maintain the recommended group size for efficient element organization and management. |
| Elements per business view | < 500 | Maintain the recommended element count for optimal visualization on the MapView page. |
Based on the protocol used by the performance and availability the maximum advisable number of monitors for a single installation monitoring up to 1,000 devices is given below.
| Protocol | Interval | Polls per minute |
|---|---|---|
| Availability | 5 min | 200 |
| SNMP and interface | 15 min | 1,000 |
| WMI and application | 15 min | 300 |
| CLI | 15 min | 150 |
| VMware | 10 min | 1,000 |
| Xen | 10 min | 500 |
Maximum Load (per installation): To ensure optimal performance, it is recommended to maintain a combined polling rate of up to 1,500 polls per minute per installation across all protocols.
| Type | Processing limit | What to know |
|---|---|---|
| Alert processing limit | 1,000 alerts per minute | Maintain the recommended alert processing rate for optimal performance. |
| Trap processing limit | 30,000 per hour | Maintain the recommended trap processing rate to ensure uninterrupted monitoring. |
| Syslog processing limit | 100 per minute | Maintain the recommended Syslog processing rate to ensure uninterrupted monitoring. |
| NetFlow processing limit | 1,000 flows per second | Maintain the recommended NetFlow processing rate for efficient flow analysis and monitoring. |
| Firewall logs processing limit | Under 1,000 logs per second | Maintain the recommended firewall log processing rate for efficient log monitoring. |
Enterprise Edition monitors multiple remote sites using OpManager Central and probe servers. These are the maximum devices, probes and related limits.
| Metric | Enterprise without Lite Central | Enterprise with Lite Central |
|---|---|---|
| Devices monitored (max) | 10,000 | 30,000 |
| Interfaces monitored (max) | 50,000 | 100,000 |
| Probes supported (max) | 100 | 100 |
The Lite Central option retains archived data at probe level, which reduces the load on the Central server's database.
If you need to monitor more than the mentioned scalability recommendations, please contact our support team at opmanager-support@manageengine.com.