JAGS
The steps outlined on this article are provided AS-IS. This means we've had reports of them working for some customers — under certain circumstances — yet are not officially supported, nor can we guarantee they'll work for your specific scenario.
You may follow through and validate them on your own non-prod environments prior to production or fall back to supported alternatives if they don't work out.
We also invite you to reach out to our Community for matters that fall beyond Atlassian's scope of support!
What is JAGS
JAGS is an internal tool developed and used by Atlassian Support to visualize data from a Support Zip file.
JAGS runs using Docker Compose and is built on top of Open Source tools:
Ubuntu sidecar to uncompress the Support Zip files.
fluentd to parse log files and import processed data to PostgreSQL.
PostgreSQL to store and persist data.
Grafana with built-in dashboards.
JAGS is able to parse Support Zip files from the following Data Center products:
Here's an example of a few built-in dashboards available after starting JAGS stack.
When to use
The primary use for JAGS is when Support Engineers are investigating a performance problem with Data Center products and Support Zip files are available.
The built-in Grafana dashboards help identifying areas of interest for further investigation.
JAGS is not a replacement to standard observability stack, but may be helpful when one is not available. It may also be useful to have an idea of possible dashboards to be built on top of your stack, based on what support engineers usually rely on.
JAGS was designed as a disposable stack, meaning it can be completely removed (containers and data) after one finishes analyzing the data.
How to run
Below is a step-by-step procedure to run JAGS stack on a computer (your own computer or a server).
| 1 | Make sure Docker Engine and Docker Compose are installed and running. Many processes on JAGS rely on multi-threaded tasks, so make sure to give a reasonable amount of resources available to the Docker Engine. |
|---|---|
| 2 | Create a directory to hold the JAGS source-code and data to be used by the containers.
Example
|
| 3 | Download the Support Zip files you want to inspect and place them in the directory you created. The structure of the Support Zip file is important to JAGS, so you are recommended to not make any changes to the file name nor its internal directory structure. |
| 4 | Download JAGS source code from here and unzip it within the directory you created on a previous step. After uncompressing the file you may have a directory structure as below.
Example
|
| 5 | Create additional needed directories and apply read and write permissions to the |
| 6 | Copy or move the target Support Zip files to the
If copying all the files within the current folder
|
| 7 | Start the stack. The only port exposed by the stack is The above command will stream the stack logs to the terminal. |
| 8 | Give it 5~10 minutes to process the Support Zip files. The time to complete may change depending on:
|
| 9 | Access Grafana through the link below.
Running on local computer
Running on remote computer
|
| 10 | To stop the stack:
|
| 11 | Data cleanup. If you know you won’t use JAGS data anymore, simply remove the |
The steps outlined on this article are provided AS-IS. This means we've had reports of them working for some customers — under certain circumstances — yet are not officially supported, nor can we guarantee they'll work for your specific scenario.
You may follow through and validate them on your own non-prod environments prior to production or fall back to supported alternatives if they don't work out.
We also invite you to reach out to our Community for matters that fall beyond Atlassian's scope of support!