Hi Chander,
sorry but I don't get what you mean. Why it shouldn't work, when there is such feature? SAP_CHECK_ACTIVE_JOBS must behave same (start/stop/after event/duration/delay) as any other job in system, no matter what exactly they does.
It's proven already, that it is working - because I can see it in alert history.
When I listed job history, we can see there was "jump" between run at 22:00 and at 23:00
So it brings me back to "Delay" properties -> tab PerformanceAttributes and section "Comparisn value" -> which is at the moment set on "Last reported value"
However when you compare 189 sec. delay at 22:00 and 46 sec. at 23:00 the difference isn't 91 sec. as reported above. It suppose to be 143 sec., so where are those 52 seconds? That would also explain, why small differencies are not reported at all, even when threshold values are set to 1+3 seconds.
This couldn't be normal, right? Is here someone, who has similar scenario working properly? At the moment it proves, that it's working but not as fast as I want (3 seconds for critical alert). I can live without that, as I will not need such strict values, anyway I'm still curious about that.