Any limitation of url_response probe concurrent profiles.
By default, the probe is configured to limit the number of concurrent profiles to 100. That is, more profiles can be defined, but the probe checks for the profiles sequentially. This may potentially lead to profiles not being executed at the scheduled time. The probe raises an alarm in this situation. You can modify this limit by editing the max_threads setting in the configuration file.
Important! You must check the resource usage of the probe when updating the max_threads setting in the configuration file. This avoids running into machine-dependent limitations for memory, threads, or connections.
The probe initially allocates min_threads threads for profile execution. If there are more profiles defined, the probe may gradually increase the number of threads. Profiles that are not immediately allocated a thread are rescheduled 20 seconds later.