Technical Monitoring - How to handle Long-Jobs in Dialog Response Time

32 Views

Hi experts,

in Technical Monitoring we are monitoring the response time of R3.

Durring the day everything is fine, as on all instaces a lot of users are on and we have always a good average.

But durring the night I always face the problem, that not many users are working and some big (long) jobs are running.

After the jobs are finished, I always get an alert that the response time was to high.

So my question is, does anybody know how to handle that thing?

I am already working with Counterthreshold (3times in 20 minutes) but I still get somes times the error.

Especially after MRP-Run with parallel-processes.

Maybe somebody have a good idea for this.

I don't want to change the limit for the night, I would prefer if I can make the check without considering the job-time.

Kind regards