[rt-users] monitoring RT

[Drew Barnes]

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
>>> 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 live connection to a working database
>>>
>>> without burning lots of CPU?
>>>
>>> Have I missed anything key to check?
>>>       
>
> On Mon, Jul 23, 2007 at 10:15:35AM -0400, Drew Barnes wrote:
>   
>> 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 and....oh, wait...
>>     
>
> 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 level services could be
> monitored easily.
>
> Nicholas Clark
>   

-- 
Drew Barnes
Applications Analyst
Network Resources Department
Raymond Walters College
University of Cincinnati