Skip to content

JIRA

Auto-Detection
Built-in Metrics

Bleemeo monitors JIRA through automatic service detection and JMX metrics collection for issue tracker performance.

Glouton automatically detects JIRA instances running on the system.

To enable metrics gathering, the Bleemeo agent must be installed with JMX enabled. See Java Metrics for setup details.

JIRA must also expose JMX over a TCP port:

  • Add -Dcom.sun.management.jmxremote.port=3333 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false to the JVM. The default JIRA startup script accepts these from CATALINA_OPTS or JAVA_OPTS environment variables.

If auto-detected parameters are incorrect, you can override them manually.

Terminal window
sudo tee /etc/glouton/conf.d/99-jira.conf > /dev/null << 'EOF'
service:
# For a JIRA running outside a container
- type: "jira"
address: "127.0.0.1"
port: 8080
jmx_port: 3333
jmx_username: "monitorRole" # by default, no authentication is done
jmx_password: "secret"
# For an additional JIRA running outside a container
- type: "jira"
instance: "NAME_ASSOCIATED_WITH_YOUR_ADDITIONAL_SERVICE"
address: "127.0.0.1"
port: 8081
jmx_port: 3334
jmx_username: "monitorRole" # by default, no authentication is done
jmx_password: "secret"
# For a JIRA running in a Docker container
- type: "jira"
instance: "CONTAINER_NAME"
address: "172.17.0.2"
port: 8080
jmx_port: 3333
jmx_username: "monitorRole" # by default, no authentication is done
jmx_password: "secret"
EOF

Glouton automatically detects configuration changes.

Metric Description
service_status Status of JIRA
jira_jvm_gc Number of garbage collections per second
jira_jvm_gc_utilization Garbage collection utilization in percent
jira_jvm_heap_used Heap memory used in bytes
jira_jvm_non_heap_used Non-heap memory used in bytes
jira_request_time Average time of request in seconds
jira_requests Number of requests per second