I started using pingstatus command in our application. It works great, but I do have a couple of problems:
My first problem is the fact that it runs just one ping. Our networks are somewhat shaky, so running several pings and getting a package loss percentage would be great. The ideal would be to add a parameter to the command such as count=... (so that I can run it like this: pingstatus url as IP count=5 ), and get back both pingdelay and pingloss or similar. I understand that it will create delays, but I can live with it.
My other problem is the pingdelay values that I'm getting: when I tested it on my Windows machine, I got all kinds of delays, usually quite small, similar to 0.000015 or even lower. However, when I moved it to the main network which consists of many (dozens to hundreds) Linux machines, most of the pingdelay values I'm getting are 0.0. Yes, that's right - a plain zero! Those which are not look like 0.00136 or so, but there are only a couple of percents of such non-zero records. What's worse - I know that I'm dealing with quite a wide network there with multiple locations and routers, so I would expect values in 20-100 ms range, not 1 ms or below.
Now, for the first problem, I should probably look into pingstatus.py - but I'm far from being a Python expert, let alone Splunk Python. A push in the right direction is all I would like.
For the second one: is there a big difference between Windows and Linux ping.py behavior?
... View more