Atlassian Monitoring with JMX (Java Management eXtension)

Want to know some details on what’s going on with your Atlassian application? (JIRA, Confluence, any JVM application).

 

Add these lines your Java Options:

-Dcom.sun.management.jmxremote.port=8686
-Dcom.sun.management.jmxremote.ssl=false
-Djava.rmi.server.hostname=SERVER.DOMAIN.COM

Create a jmxremote.password file

  1. Copy C:\Program Files\Atlassian\JIRA\jre\lib\management\jmxremote.password.template to C:\Program Files\Atlassian\JIRA\jre\lib\management\jmxremote.password
  2. Edit jmxremote.password to add your credentials
  3. Set permissions on jmxremote.password
    1. Set owner the the user your Atlassian application runs as
    2. Remove inheriting permissions
    3. Remove all account permissions except for owner
    4. save your settings

Start your service & launch jconsole

Note: Running jconsole.exe -debug is helpful for troubleshooting

Use your favorite monitoring tool to collect the stats

SolarWinds SAM module supports JMX

Performance Monitoring for Atlassian Applications (JIRA, Confluence on Windows)

Who doesn’t want to know how their applications are performing? Here’s a quick way to start collecting data and analyzing it.

  1. Sign-up for a free New Relic account
  2. Download your New Relic java agent zip file to your server and extract. I placed mine in the “D:\Program Files” folder.
  3. Edit “D:\Program Files\newrelic\newrelic.yml”
    1. update the “license_key” and “app_name” variables
      1. note: the license_key is surrounded in ticks ” and app_name is not.
  4. Configure the java agent to start when the service starts
    1. start > run > regedit.exe
    2. HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Apache Software Foundation\Procrun 2.0\[App ID]\Parameters\Java
    3. edit “Options” by adding “-javaagent:D:\Program Files\newrelic\newrelic.jar” to the bottom
  5. Restart your application service

If your app doesn’t show up in the console check your logs! (D:\Program Files\newrelic\logs\newrelic_agent.log)