In OpManager, every device template will have a predefined availability monitoring interval by default. This monitoring interval is applied to all the corresponding devices during device discovery. You can customize this according to your preference.
For example, if your network has a set of critical servers or devices that needs to be observed with utmost importance, you will expect OpManager to alert you the instance that device under performs or goes down. Such components in your network can be customized with smaller monitoring interval, so that OpManager will closely monitor it for availability according to the specified time span.
For an efficient monitoring, a knowledge about the current load of SPOLL (availability monitoring) in OpManager is important. This can be calculated by the formula,
Number of managed devices/ Monitoring interval (Average)
The maximum recommended load for availability monitoring is 200 polls/min. For example, consider that you have 1000 devices in a single instance with 5 minute monitoring interval. Here, the load will be 1000/5 = 200 polls/min. This implies that the availability monitoring load factor has reached to the maximum limit.
Similarly, if you wish to add 1 minute monitoring interval, you should have lesser number of devices added to match the specified load factor (200 polls/min). In such cases, you can have only 200 devices at maximum with a 1 minute polling interval and it is not advised to add more devices for availability monitoring since the existing load has already reached the max limit of 200 polls/min.
In addition, the load of availability monitoring also depends on the monitoring interval and count of other entities monitored in OpManager such as interfaces, performance monitors, etc. Please refer to our Scalability Recommendations document to optimize OpManager for better performance and efficiency.