Monitoring your Atlassian server with Bleemeo

In this article we will show you how:

• To configure Atlassian server to Bleemeo to automatically collect metrics with Bleemeo auto-detects
• To configure a dashboard to better understand your server and what's going on:
  • An automatic dashboard
  • A custom dashboard

What is Atlassian stack?

Atlassian Corporation is one of the largest companies providing tools for project management and software development, among these tools is The Atlassian Stack. It's the possibility to deploy the Atlassian product on your server and don't use obligatory the Cloud of Atlassian. It's also a bundled offering that combines every Atlassian Server or Data Center product. Now Atlassian stack doesn't exist with this name because your choice between the Atlassian Server or Atlassian Data Center.
The difference between Bitbucket server and the data-center that is the Bitbucket server is a single on-premise instance of Bitbucket. For teams that require high-availability, performance at scale, and smart mirroring for distributed teams we offer Bitbucket Data Center, an active-active cluster of Bitbucket Server nodes. If your team prefers a single server installation, download a free trial of Bitbucket Server.

How to configure Atlassian server to Bleemeo?

To configure your Atlassian server, Bleemeo agent needs to be installed with JMX enabled, see Java Monitoring for setup details. Also, if you want to configure Bitbucket, Confluence or Jira, follow the instruction bellow:

• Bitbucket needs to expose JMX over a TCP port. To enable JMX you can follow Enabling JMX counters for performance monitoring on Atlassian documentation. Here is a summary for unauthenticated access:

  • Add the options below to the JVM. Default Bitbucket startup-script accepts them from JMX_OPTS or JAVA_OPTS environment variable.
  -Dcom.sun.management.jmxremote.port=3333 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false
  • Add to $BITBUCKET_HOME/shared/bitbucket.properties
  jmx.enabled=true

  Warning: this will allow unauthenticated access. Make sure no untrusted access to this port is possible or you should setup authenticated JMX access.

• Confluence or Jira need to expose JMX over a TCP port. To enable JMX you need to:

  • Add the options below to the JVM. Default Confluence or Jira startup-script accept them from JMX_OPTS or JAVA_OPTS environment variable.
  -Dcom.sun.management.jmxremote.port=3333 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false

  Warning: this will allow unauthenticated access. Make sure no untrusted access to this port is possible or you should setup authenticated JMX access.

If you need more information, you can consult our documentation.

Default dashboard

Once the Bleemeo agent has been able to Atlassian Stack access, a new default dashboard appears. This looks like:

How to create your dashboard?

Now let's see how to make custom dashboards that cans better meet your specific expectations. For example, we will monitor metrics:

• The number of pushes per second
• The number of pulls per second
• the status of Bitbucket

if you want more Atlassian metrics here is a link to our documentation.

This type of dashboard allows you to better know when there are people connected and how many, and also what is happening on your server. You can also add other metrics, if you run your server on a docker for example you can add:

• Status of Apache docker
• Memory used by applications in percent
• CPU used in percent.

It will allow you to have a single dashboard for several types to monitor and therefore a dashboard is infinitely customizable, which can be useful for what you need exactly to monitor. With Bleemeo, you can start monitoring Atlassian server metrics and create custom dashboards in a few minutes.
If you don't have a Bleemeo account yet, start monitoring your Atlassian server today in 30s.