I have the scenario where logmon is monitoring one log file and due to the volume that goes into the log it runs logmon at 100% CPU and ultimately logmon is unable to keep up with reading the file.
Even with the one profile and no defined watchers, logmon is unable to keep up.
Are there any configuration options that might affect the overhead of reading a log file that could be adjusted or checked?
File updating at 4mb/sec rate
UIM - LOGMON PROBE
Unfortunately there is no tweaking that can be done here - the logmon probe is a C-based probe and does not have the same options for allocating memory/resources that might be found in a Java-based probe.
The probe will essentially work as fast as it can at all times; increasing the power (CPU/faster disks/ram speed/etc) of the underlying hardware is the only thing that can really be done to improve performance.