You might consider using Nagios or Check_MK with a call to the Jenkins API to check if the server is running and is not being shutdown.
I use this call to Nagios check_http in our Nagios setup: $USER1$/check_http -I $HOSTADDRESS$ -u /api/xml?depth=0 -R quietingDown.false $ARG1$ That checks the HTTP server at $HOSTADDRESS$ with the url /api/xml?depth=0 and returns a failure if the HTTP server does not respond or if the HTTP server response does not include the text quietingDown.false. That isn't as sophisticated a monitoring system as I envision we will have eventually, but it reports if the server is available, running, and not shutting down. That has been enough to answer most of the availability questions I had. I believe R. Tyler Croy has already configured a sophisticated Nagios based monitoring system for the Jenkins production servers. Mark Waite >________________________________ > From: Jeti <saxo...@gmx.de> >To: jenkinsci-users@googlegroups.com >Sent: Friday, June 15, 2012 8:36 AM >Subject: Some way to send an isalive test to a jenkins server? > > >Hi, > >I would like to use Jenkins jobs to schedule tasks in my company. Problem is >that reliability is an issue then. The Jenkins server breaking down without >anyone noticing would be a problem. Is there some some kind of isalive service >built into the Jenkins server so that some pool can send periodoc isalive >checks? Just checking whether calling the url the Jenkins server is hooked to >and seeing whether an http error comes back or not seems not a sufficient test. > >Thanks, Jeti > > >
