Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Overview and practical use cases with open source tracing tool for Java Apps. Glowroot. Installation

Hi team, 

today let's do installation.



Installation of the application is quite simple on agents, and this article shows a scheme for working with a built-in collector, but for industrial installations we use it with a bundle with elasticsearch.

The installation can be both for individual nodes and so for the central collector. In this case, consider for a separate node.



  • {jira_home} - is location of Jira home directory.
  • {jira_installation_directory} is the location of Jira installation directory.



  • Downloading the installer
wget -c
  • To check, create a directory via command
  mkdir -p /{jira_home}/glowroot/tmp
  • Let the Jira process write and set ownership for simplicity, but it is recommended that you just give the write ability to the owner of the Jira process.
chown -R jira: /{jira_home}/glowroot
  • We additionally set the argument to in the jira installation directory, in our case it is /jira/current/bin. By default, Atlassian uses the /opt/atlassian/jira/bin directory and add the following line in the file
JVM_SUPPORT_RECOMMENDED_ARGS="-javaagent:/{jira_home}/glowroot/glowroot.jar ${JVM_SUPPORT_RECOMMENDED_ARGS}"
  • After we restart the application via: 

systemctl restart jira

  • And best practice is monitoring for errors by
tail -f {jira_installation_directory}/logs/catalina.out 
  • Since the default address is, go to the directory in glowroot and see that there are files such as admin.json. In that file, you can change bindAddress to or whatever you require. In my case, I will add contextPath - /glowroot.
  • And then on reverse proxy, add configuration on nginx like this
location /glowroot {

          on httpd like this

ProxyPass        /glowroot
ProxyPassReverse /glowroot

Additionally, you can look at the attached documentation


As a result, at our address, sees transactions with percentiles.




Log in or Sign up to comment

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you