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

-

In that small article, you can find how to install the agent of Glowroot.

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.

image.png

Prerequisites:

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

 

Steps:

  • Downloading the installer
wget -c https://github.com/glowroot/glowroot/releases/download/v0.13.6/glowroot-0.13.6-dist.zip
  • 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 setenv.sh 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 127.0.0.1, go to the directory in glowroot and see that there are files such as admin.json. In that file, you can change bindAddress to 0.0.0.0 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 {
         proxy_pass http://127.0.0.1:4000;
}

          on httpd like this

ProxyPass        /glowroot  http://127.0.0.1:4000/glowroot
ProxyPassReverse /glowroot  http://127.0.0.1:4000/glowroot

Additionally, you can look at the attached documentation

https://github.com/glowroot/glowroot/wiki/Agent-Installation-(with-Embedded-Collector)

 

As a result, at our address, jira.example.com/glowroot sees transactions with percentiles.

 

image.png

Comments

Post a Comment

Popular posts from this blog

How only 2 parameters of PostgreSQL reduced anomaly of Jira Data Center nodes

-
Image
  Hello community, Gonchik Tsymzhitov is in touch. Today, I would like to share with you a short story about postgresqltuner.pl in usage.  So from previous articles I hope you configured the PostgreSQL server and postgresqltuner.pl.  After executing command, ./postgresqltuner.pl --ssd for ssd disks server. You can see like this output: postgresqltuner.pl version 1.0.1 [OK]      I can invoke executables Connecting to /var/run/postgresql:5432 database template1 as user 'postgres'... [OK]      The user account used by me for reporting has superuser rights on this PostgreSQL instance =====  OS information  ===== [INFO]    OS: linux Version: 5.4.17-2036.102.0.2.el8uek.x86_64 Arch: x86_64-linux-thread-multi [INFO]    OS total memory: 41.03 GB [OK]      vm.overcommit_memory is adequate: no memory overcommitment [INFO]    Running under a vmware hypervisor [INFO]    Currently used I/O sc...
Read more

Stories about detecting Atlassian Confluence bottlenecks with APM tool [part 1]

-
Image
  Hey! Gonchik, a lover of APM (application performance monitoring) tools, in particular Glowroot, is in touch. Today I will tell you how to find bottlenecks in Confluence On-Prem in the shortest possible time based on one industrial installation. We are faced with a situation where a large number of people simultaneously break into the knowledge base on Confluence On-Prem (during the certification), and the Confluence dies for some time. We immediately thought that the problem is precisely in the simultaneous number of visitors and we can immediately tweak the JVM, but it turned out that not everything is so simple. Below I will tell you how we found the real cause of the brakes and how we dealt with it. The main task: to conduct an audit and, on its basis, achieve performance improvements, especially in times of a large number of active users in the system. Of course, first of all, the hardware resources and OS configurations were checked, where no problems were identified. Howev...
Read more

Atlassian Community, let's collaborate and provide stats to vendors about our SQL index usage

-
  Hi!  Gonchik is in touch. Today I would like to get a little bit of help from you related SQL indexes on your Jira installation (Data Center, Server edition does not matter).    I would like to share a story about  PostgreSQL  and  Jira 8.13.3  ( JSD 4.13.3 )  release.  In that post I will be happy if you answer and comment about your instance indexes, as those info can help to improve the existing situation of heavy indexes.  Typically, it starts from improvement of configuration (e.g. using  https://postgresqltuner.pl/ ),  then query analyzing, adding indexes, after removing as heavy one (shortly  https://wiki.postgresql.org/wiki/Index_Maintenance ) :)    I use like this query in PostgreSQL: SELECT s.schemaname,        s.relname AS tablename,        s.indexrelname AS indexname,        pg_size_pretty(p...
Read more