By latency, I think you are talking about ICMP echo requests ms response time, like you would get with a Ping?
C:\Users\brolly33>ping 1.1.1.1
Pinging 1.1.1.1 with 32 bytes of data:
Reply from 1.1.1.1: bytes=32 time=6ms TTL=59
Reply from 1.1.1.1: bytes=32 time=4ms TTL=59
Reply from 1.1.1.1: bytes=32 time=6ms TTL=59
Reply from 1.1.1.1: bytes=32 time=11ms TTL=59
Ping statistics for 1.1.1.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 4ms, Maximum = 11ms, Average = 6ms
We don’t have a relevance inspector that tests for this directly.
Solution would be to write an Action that performs each of the Pings for each location you want to test and redirect the output to a local file. Then you would take the action on the endpoints. Then you could use an analysis that reads the file for the time= portion, for reporting in the console and upstream.