search

atlassian-labs / Jira-DC-Grafana-Dashboards

Apache License 2.0
12 stars 2 forks source link

Problem with jmx-exporter settings for jira #6

Open SD3vEng opened 1 year ago

SD3vEng commented 1 year ago

Good afternoon! We have jira version 7.6, I do everything according to the instructions: https://confluence.atlassian.com/doc/monitor-application-performance-1115674751.html

I take jmx-exporter-config.yml with https://github.com/atlassian-labs/Jira-DC-Grafana-Dashboards

I download jmx-exporter myself from https://github.com/prometheus/jmx_exporter

In seten.sh prescribe CATALINA_OPTS="-javaagent:/root/jmx_exporter/jmx_prometheus_javaagent-0.17.0.jar=8098:/root/jmx_exporter/jmx-exporter-config. yml ${CATALINA_OPTS}"

And after launching jira, the error logs, As I understand the problem is due to jmx-exporter-config.yml image

How can I solve the problem

Wil312 commented 1 year ago

Can you please post the contents of your jmx-exporter-config.yml file?

SD3vEng commented 1 year ago

downloading > https://github.com/atlassian-labs/Jira-DC-Grafana-Dashboards/blob/main/jmx-exporter-config.yml

image

Wil312 commented 1 year ago

We have jira version 7.6

That's quite an old version. Which version of the jdk is it running on?

atl-mk commented 1 year ago

I was able to successfully start Jira 7.6.17 with the Prometheus JMX exporter 0.17.0 Java agent.

Few things to check

1 - The OS user account that Jira runs in (which can be named jira, and can be different to the admin's user account) has access to both the exporter and the config file 2 - The path to the JAR is correct 3 - The settings (the port, and the location of the config file) are delimited by a = character, not a : character. I can see from your screenshot that isn't the case though, otherwise the error message would have been: Error opening zip file or JAR manifest missing : /root/jmx_exporter/jmx_prometheus_javaagent-0.17.0.jar:8098:/root/jmx_exporter/jmx-exporter-config.yml 4 - The path is absolute

I also recommend that you upgrade if you can, especially if it's public facing, 7.6 was last patched in 2019 and certainly has critical security vulnerabilities. On that note, Jira also shouldn't be run by the root user.