Services - Make ##SERVICERESPONSE## available to Overall alerts

18 hours ago, thanh rodke said:

The average of all test location response times would be ideal for diagnosing slow connections as well as down connections.. 

Oooh, yes that would be awesome as well.

On 7/22/2016 at 9:23 AM, Joe Tran said:

I would love it if we could reference ##SERVICESRESPONSE## on an overall alert. We don't deliver alerts for singular test location failures, since our mandate to only notify on systemic issues across all test locations.

So the question will probably, which response to include in the event there are differing responses? Why not include all of them!    Or only include the first one in the test location array for that service. Or pick a random one. Or arbitrarily decide certain failure reasons have a "higher" priority than others and choose the "highest" one.

 

The average of all test location response times would be ideal for diagnosing slow connections as well as down connections.. 

Would like to see this too.