Home / server / Questions / 106853
Accepted
Tim Howland
Asked: 2010-01-28 08:10:49 +0800 CST

Best practices for monitoring a JIRA installation?

  • 772

One of my clients has a confluence / JIRA system set up. They've been having some issues- outbound email gets wedged, etc. If you support a JIRA install, what do you monitor? Do you use JMX? Direct DB queries? Occasional SOAP requests to the API?

I'll be monitoring using Nagios / NRPE, but will write any needed support scripts directly, so any technology that runs on a linux box is probably fine.

monitoring nagios jmx nrpe jira

2 Answers

  1. Best Answer

    I use Nagios / NRPE for our JIRA server (which also runs Confluence), together with Munin for tracking resources over time (handy for looking for memory / CPU spikes, excessive DB accesses, etc.)

    Apart from the standard checks that come with NRPE, I added the following for JIRA:

    • A check_http check that makes sure the application is up
    • A check_file_age check that verifies the JIRA backup file has created and is the expected size.

    We set up an external SMTP server in our JIRA instance, so there's not much to check regarding email; if you have your outgoing mail server running on the JIRA machine, you could add a Nagios check to make sure its outgoing mail queue isn't getting too full (Munin also monitors this by default). You could also maybe use a WebInject test to log into JIRA and go to the admin page that shows the size of the mail queue.

    • 3

  2. You can use snmp with jboss (of course you need to have jira on jboss).

    You can then access to a lot of data like thread pools, datasources ...

    See JBossSNMPAdapter and JBossSNMPAdapterGetValues

    You can use cacti to graph the data, this can be very useful to handle problems: cacti forum.

    • 3