Possible back-end problem – response time repeatedly too high

In case the EVENT_WR-H-back-end-500 warning (Possible back-end problem - response time repeatedly too high) appears frequently, this can have the following causes:

  • A network problem in the back-end network.
  • An overall bad performance of back-end server(s).
  • Complex requests.

This event is generated if 4 backend requests within 2 minutes need more than 3 seconds each and can be configured in the logsurfer.conf.user.custom file as described in the article Customizing events.

Example:

# responsetime is higher than 3 seconds 5 or more times in 2 minutes 
WR_SG_SUMMARY_BackendResponseTime_enable=true 
WR_SG_SUMMARY_BackendResponseTime_num=5 
WR_SG_SUMMARY_BackendResponseTime_range=120

Since the bad response time affects the overall system performance, it should be fixed soon. Each pending request consumes resources on the Airlock Gateway. The total time each request takes is almost as important for the performance as the total number of requests per second.

In this case, we do not recommend event adjustment, which could only suppress the symptoms instead of addressing the causes.