Agent availability or connected agent measure not working at lower threshold value
I have added a measure for connected agent and with agent group as filter.
I have kept lower threshold as 0 so that if agent is not available (application is not available) it should create an incident. It was working in DT 5.1 but seems like not in 6.0.
Best Answer
Hi
actually, I was slightly wrong. There is a way to make it work if you want to use the agent availability measure from the functional health group with a custom incident rule. I have just tested it (on 6.2) and it seems to be fine.
Create your measure as usual but when defining your incident rule, make sure that the aggregation is set to count. The incident should now fire when the agent goes off-line. Don't forget to set your lower severe threshold on the measure to 0 of course.
Regards
Flo
Hi ..
Thanks for resolution. Its working when set it count.
Hi
for 6.0 there is an out of the box alert anyway called application process unavailable so you should use this one instead.
But, if you want to set up your own alert you will encounter a small problem...
Incidents and thresholds only work when data is available. When the agent goes down, it cannot send any data (i.e. you won't get a 0, just nothing) so the threshold won't detect the problem as it needs a value.
I'm not too sure why it worked on 5.1 but most of my knowledge is with 6.x.
Regards
Flo
application process unavailable does not have condition feature which has threshold defined or agent group. I am sure it was working in 5.x becasue we are using same incidents in 6.x...
Let me know if there is any change from 5.0 to 6.0 for measure --> server side performance--> functional Health -->Avaibility --> connected agent or avaibility of agent.
