Report require for Machine Latency

Need the below details from all end user devices

Devicename, Device IP, time , User name, minimum Latency to Chicago core(10.x.x.x),max Latency to Chicago core(10.x.x.x),average Latency to Chicago core(10.x.x.x), minimum Latency to Carmel Core(192.x.x.x), max Latency to Chicago core(192.x.x.x), average Latency to Carmel core (192.x.x.x), minimum Latency to Philly Core(172.x.x.x), max Latency to Philly core(172.x.x.x), average Latency to Philly core (172x.x.x)

any thought about Latency analysis for such report.

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.

1 Like

Example Action Script

wait cmd.exe /C ping 1.1.1.1 > "{pathname of data folder of client & "\PingTest1.1.1.1.txt"}"
setting "Ping1.1.1.1"="{preceding text of first "ms" of following text of first ", Average = " of line whose (it contains ", Average = ") of file "PingTest1.1.1.1.txt" of data folder of client|"error"}" on "{parameter "action issue date" of action}" for client

wait cmd.exe /C ping 1.1.1.2 > "{pathname of data folder of client & "\PingTest1.1.1.2.txt"}"
    setting "Ping1.1.1.2"="{preceding text of first "ms" of following text of first ", Average = " of line whose (it contains ", Average = ") of file "PingTest1.1.1.2.txt" of data folder of client|"error"}" on "{parameter "action issue date" of action}" for client

You would run this action on your endpoint, and the endpoint would ping 1.1.1.1 and record the results in PingTest1.1.1.1.txt. Then it would read PingTest1.txt and set a client setting called Ping1.1.1.1, which would show up in the console as a setting.
Repeat for other IP addresses you want tested.

4 Likes

While I understand the desire, and @brolly33’s Action Script would fit the need, keep in mind this only shows the latency as of the last time it was run prior to the last report time.

There are plenty of Network Monitoring solutions that track this over time, giving you graphs of latency and packet loss over time, customizable frequencies (how often to ping, how many pings to send, what size of pings, etc), HTTPS and SSH monitoring capability, and the ability to poll SNMP or receive SNMP traps.

BigFix is great, but as they say, “when all you have is a hammer, every problem starts looking like a nail.”

2 Likes