Though it can take more options, it's simplest usage is this:
Which logs any problems pinging 220.127.116.11 (google-public-dns-a.google.com) to outages_18.104.22.168.txt, e.g.:
If you want to tail that file, in another terminal window, or even on another computer if you log to a share, do:
Outage started 2015-03-13 22:05:56 -0400 (No route to host) and ended 2015-03-13 22:06:06 -0400 Outage started 2015-03-13 22:06:12 -0400 (No route to host) and ended 2015-03-13 22:06:16 -0400 Outage started 2015-03-13 22:06:32 -0400 (No route to host) and ended 2015-03-13 22:06:36 -0400
The output is not 100% accurate because long ping times (over 500ms by default) would be considered an outage, where it really may be a latency issue. Also, the reason specified for the outage is only the first error that comes back from what is assumed to be a failed ping, and that reason could change over time. Netout assumes you care more about the outages and their duration over a longer time period and logging those to a file. That's all it does.
tail -f outages_22.214.171.124.txt
And if you need something more, here are some other free tools:
- Ping - Just using "ping 126.96.36.199 >> ping.log" is a great way to collect data to provide to an ISP, etc. about outages.
- Nagios - free monitoring tool that's been around a long time and is a good choice for your organization, but overkill for simple monitoring.
- MRTG - I remember this being used many years ago and is a great free tool. It is also overkill for just logging ping outages. This is what you use if you want to tinker and create your own outage page.
- Smokeping - seems like a good tool, but at the time of writing, there was no (OS X) Homebrew recipe for it, and I didn't have time to perform the installation.
- mtr - also been around a long time. It is like a minified console version of the above types of graphing tools with a one character status for checks, so it is easy to see status of lot of hosts at once.