Getting the following major alarm from the url_response probe:
Web_AEM_Publish Intranet Test device port 4503 is delayed because no thread is available
Need to stop these alarms from being generated or change the severity of the alarm.
How do you prevent the url_response probe from generating the "no thread is available" alarm or reduce the severity of the alarm?
url_response probe: 4.43
Since the 3.60 release of the url_response probe, the Delayed alarm with the "no thread is available" reason is suppressed only for the first run of a profile. After that, the current design of the probe does not allow you to stop it from sending this alarm out if the condition is met.
The Delayed alarm is generated by the url_response probe for several different reasons:
- profile is already running
- probe unable to create thread
- no thread is available
The probe will issue the Delayed alarm for the first 2 conditions even if it is the first time that the profile is executed. Since it is not possible to stop the probe from generating these alarms, to completely eliminate processing of this particular Delayed alarm, it would be necessary to add an Auto Operator Preprocessing rule in the nas configuration to exclude the Delayed alarms with the "no thread is available" reason that are generated by the url_response probe.
To change the severity level of the Delayed alarm generated by the probe, from the Messages tab of the url_response probe's Configure GUI, change the level of the Delayed alarm to the desired level. Once this change is made, when the probe detects any of the delay conditions that will generate this alarm, the alarm will be raised with the new severity level specified. Note that by changing the severity of the Delayed alarm, it will be applied to all of the Delayed alarms generated by the probe. There is no way to specify a different alarm for the 3 conditions that generate a delay alarm with the current design of the probe.