DX - IM - how many profiles webservices probe can handle - best practices


Article ID: 210602


Updated On:


CA Unified Infrastructure Management On-Premise (Nimsoft / UIM)


DX - IM - how many profiles webservices probe can handle - best practices


Any UIM version

Any webservices probe version



Robot Environment for Running Probes

Robot Machine Considerations
Nimsoft probes are typically run on robots that connect to a hub which connects to the primary hub. For the listed
probes, the following best practice is suggested for selecting machine configuration for the robot that runs them:

 Machine type – physical or Virtual(VM)
 HA Configuration – Not required
 Machine CPU Compute – 2 to 4 core 64bit Pentium or equivalent with speed of 2.0 Ghz with 50% available
on average
 Machine system memory – 4GB to 8GB
 Machine disk storage – 72GB available
 Machine Network bandwidth – standard LAN connectivity bandwidth e.g. 1Gbps. For better results, robot
machine should be in the same subnet as the devices monitored by the probes running on that robot
 Operating Systems – All robot supported OSs e.g. Windows server os– e.g. W2K8R2 or later, Enterprise
Linux v6.1 or later

Network latency and connectivity Considerations
The listed probes are network latency and packet drop sensitive. During testing we considered a latency of less
than 100ms between the Hub and robot. The latency between the probe and the tested application is recorded as
part of the measurements.

Number of devices or profiles per Probe – Key Considerations
Number of devices or profiles monitored by one instance of the probe also affects performance of the probe and
proactive measures below can assist you in making the probe performance optimal for your environments.

Key Configuration Restrictions
1. Size of the CFG file should be less than 3MB.
2. At very high number of profiles (1,000), alarms may get delayed up to 15 minutes in a worst case scenario
(all WSDL’s not responding). DE13537
3. Do not Edit and De-Activate the probe within 15 minutes of each action. 

Probe Metrics Count and Runtimes Considerations