Answer the question
In order to leave comments, you need to log in
How to collect statistics of the long work of the ping command?
Has anyone encountered collecting statistics on the work of the Ping command?
The task is this: to ping a device on the network in large packets for a long time (the device is available 24/7, besides, monitoring is involved in its availability), then for a period of time it is necessary to look at the maximum response time.
Example: we ping the device for 24 hours, the ping logs are written somewhere. We stop work. Let's go look at the ping command processing logs for 24 hours, sort by response time.
Answer the question
In order to leave comments, you need to log in
0. Open the cmd command line
1. ping -t -l 1024 127.0.0.1 >> log_ip.txt
2. After 24 hours or as you get bored - press CTRL + C or CTRL+BREAK.
3. Open log_ip.txt in Excel, separate the text into columns (the separator is a space) and build any report.
MTR / WinMTR
Slightly not for that, of course, but cross-platform, lightweight, can import anywhere
If the availability of the device is already being monitored - what prevents you from attaching ICMP pings to the same monitoring? You can save history, build graphs and export data in any format.
via the command line
Execute the ping command cmd ping -4 -n 220 yandex.ru
You can Download WinMTR Parameter
decoding: WinMTR
Host name - the name of the host through which the packets pass.
No — serial number of the node.
Lost % - the percentage of losses on the node; calculated from the sum of lost packets on the host.
Sent is the number of packets sent to the host.
Recv is the number of packets received from the node.
Best - the best ping value.
Avrg - average ping value.
Worst is the worst ping value.
Last - last ping value.
( The number of packets sent and the number of received should be the same )
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question