There are tools we use every day that practically need no introduction.
Ping is one of them.
And all my respect to those who have maintained it for decades: it continues to do what it was created to do exceptionally well.
But often, when a ping fails, the real work has just begun.
Is it the destination? My gateway? The internet connection? Am I experiencing loss? Is latency increasing? Is it a one-off issue, or is the connection degrading?
That's where Spring came in.
The idea was to take one of the most basic network diagnostic tools and give it more context, without losing what makes it great: opening a terminal, typing a command, and getting an immediate response.
With the new release, Sping continues to grow around that idea: sping 8.8.8.8 And in a single view, you can see latency, jitter, loss, trend, connection quality, gateway, WAN, TTL, approximate hops, and degradation/recovery events.
You can also monitor multiple destinations simultaneously, use it in batch mode, or consume its NDJSON output from scripts and automations. All in Rust, cross-platform, independent of system ping, and in a binary of around 1.5 MB.
The video below shows much better than any explanation what I wanted to achieve with
👇 🔗 GitHub: https://github.com/LambdaBytes/sping
And one thing that has been especially useful since I made it public: people testing it on networks and systems that I couldn't reproduce are finding small edge cases and helping to improve it release after release.
#opensource #rust #networking #linux #windows #macos #devops #sysadmin #cli
Top comments (0)