- Check if there is any logmon probe on the affected robot.
- If so, deactivate it. If after deactivating the logmon probe the CPU usage of the hdb.exe drops down to normal, you will know that is logmon what is causing this issue.
- Drill down into the different logmon profiles and try to locate which profile/s is overloading the robot.
- Locate any profile where logmon is scanning a very large number of log files (Eg. using wildcards *.log) and/or with a polling period too short (5 sec).
The same is applicable to ntevl