Currently there is no way to modify the Alert parameters. They are exposed for informational purposes. If needed, you can modify the scan settings to adjust accordingly (if you find sessions are being dropped due to timeouts).

hello

regards this case and  DAST Scan Show an error : Alert Excessive response time 

 In clients enviroment two DAST sensors (docker) and WebIsnpect (stand alone) works on same server. The problem described above persist only on DAST sensors. The problem has been occurring for two weeks and occurred several weeks after the update Fortify to 24.2 (from 23.2).
There were no major configuration changes.

Thank you 
-- 
Pawel

hello

regards this case and  DAST Scan Show an error : Alert Excessive response time 

 In clients enviroment two DAST sensors (docker) and WebIsnpect (stand alone) works on same server. The problem described above persist only on DAST sensors. The problem has been occurring for two weeks and occurred several weeks after the update Fortify to 24.2 (from 23.2).
There were no major configuration changes.

Thank you 
-- 
Pawel

This alert is informational and generally indicates latency on the part of the network and/or the scan target.  If the latency were to increase, then there is another scan setting ("Consecutive Timeouts") which would halt the scan altogether, waiting for the "network problem" to be addressed and then a human to Resume the scan.

If this error only occurs for the Dockerized scan machines (assuming same scan targets and everything the same as for WebInspect), then I would wonder if there were a defect and try with any newer images if they become available.  Barring that you are on the latest image build number, then I would reconsider the Docker network and settings.  Were these new images being Run exactly the same as the prior sensors?  Have you tried downgrading one of them to the prior image version to see if the latency persists?  Are there resource changes or issues on the Host Server for these scan machines?