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...
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? > > Nicholas Clark > _______________________________________________ > http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users > > Community help: http://wiki.bestpractical.com > Commercial support: [EMAIL PROTECTED] > > > Discover RT's hidden secrets with RT Essentials from O'Reilly Media. > Buy a copy at http://rtbook.bestpractical.com > -- Drew Barnes Applications Analyst Network Resources Department Raymond Walters College University of Cincinnati _______________________________________________ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: [EMAIL PROTECTED] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
