Basic monitor for a website or API looking at HTTP response codes

curl --write-out %{http_code} --connect-timeout 10 --max-time 20 -s -I -L http://google.com --output /dev/null
Basic check to see if a website (or even an API) is responding as expected. If this is put in a case statement, there would be enough flexibility to monitor just about anything that gives an HTTP response code, as well as the network path to the site looking at curl exit codes. As this is for a possible monitor, timeouts have been added to make sure that iteration overruns do not occur. ( hopefully, curl sometimes "sticks" longer than expected )
Sample Output
200

0
By: Guyverix
2015-09-19 17:29:32

What do you think?

Any thoughts on this command? Does it work on your machine? Can you do the same thing with only 14 characters?

You must be signed in to comment.

What's this?

commandlinefu.com is the place to record those command-line gems that you return to again and again. That way others can gain from your CLI wisdom and you from theirs too. All commands can be commented on, discussed and voted up or down.

Share Your Commands



Stay in the loop…

Follow the Tweets.

Every new command is wrapped in a tweet and posted to Twitter. Following the stream is a great way of staying abreast of the latest commands. For the more discerning, there are Twitter accounts for commands that get a minimum of 3 and 10 votes - that way only the great commands get tweeted.

» http://twitter.com/commandlinefu
» http://twitter.com/commandlinefu3
» http://twitter.com/commandlinefu10

Subscribe to the feeds.

Use your favourite RSS aggregator to stay in touch with the latest commands. There are feeds mirroring the 3 Twitter streams as well as for virtually every other subset (users, tags, functions,…):

Subscribe to the feed for: