Re: [rt-users] monitoring RT

- Nicholas Clark [EMAIL PROTECTED] wrote: We're going to make the RT self-service interface visible to our external clients. We'd like to monitor it, so that we know if it's down? What's the best way to monitor RT? Are there any built in pages that would let us quickly tell that (say)

Re: [rt-users] monitoring RT

We also have a basic perl script using WWW::Mechanize which opens the login page, logs in with a 'nagios' user and ensures it gets a valid response (we check for a 200 OK and that the content matches RT at a glance. If this fails it generates a critical nagios alert and wakes the on-call

[rt-users] monitoring RT

We're going to make the RT self-service interface visible to our external clients. We'd like to monitor it, so that we know if it's down? What's the best way to monitor RT? Are there any built in pages that would let us quickly tell that (say) 1: users can log in 2: the RT web application has a

Re: [rt-users] monitoring RT

Nagios (or something similar) monitoring each of the services seems the easiest way to me. And if RT goes down, just have Nagios send an alert into RT andoh, wait... Nicholas Clark wrote: We're going to make the RT self-service interface visible to our external clients. We'd like to

Re: [rt-users] monitoring RT

I suppose I've gotten lucky and never had this happen. One option to check for that is hire a journalism major to hit F5 a lot and make sure the site is working. ;-) Nicholas Clark wrote: Nicholas Clark wrote: We're going to make the RT self-service interface visible to our external

Re: [rt-users] monitoring RT

Nicholas Clark wrote: Nicholas Clark wrote: We're going to make the RT self-service interface visible to our external clients. We'd like to monitor it, so that we know if it's down? What's the best way to monitor RT? Are there any built in pages that would let us quickly tell that (say) 1:

Re: [rt-users] monitoring RT

PROTECTED] al.com cc rt-users@lists.bestpractical.com Subject 07/23/2007 09:17 Re: [rt-users

Re: [rt-users] monitoring RT

On Mon, Jul 23, 2007 at 09:22:31AM -0500, James Moseley wrote: That's why folks hire system admins - so when things stop working, they can restart them. ;-) Other than monitoring HTTP and MYSQL via Nagios, you could always write a Nagios plugin that would bring up the RT login page and login

Re: [rt-users] monitoring RT

Nicholas Clark wrote: Yes, but this doesn't catch the case where the web server is working, the database is working, but the mod_perl has got itself into a state where the database handle is invalid and spewing errors, but DBI still thinks that it's connected. I was already assuming that the low

AW: [rt-users] monitoring RT

- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im Auftrag von Nicholas Clark Gesendet: Montag, 23. Juli 2007 16:36 An: James Moseley Cc: rt-users@lists.bestpractical.com; [EMAIL PROTECTED] Betreff: Re: [rt-users] monitoring RT On Mon, Jul 23, 2007 at 09:22:31AM -0500, James Moseley wrote: That's

Re: [rt-users] monitoring RT

On Jul 23, 2007, at 7:17 AM, Nicholas Clark wrote: Nicholas Clark wrote: We're going to make the RT self-service interface visible to our external clients. We'd like to monitor it, so that we know if it's down? What's the best way to monitor RT? Are there any built in pages that would

Re: [rt-users] monitoring RT

If that's all that's required, then the check_http plug-in provided by Nagios will do the trick. There's an option to check the html for the presence of a text specific string (maybe Search/Results.rdf - you'll only get this string after successfully logging in). Saves you the trouble