JIRA

Auto-Discovery

Health Check

Metrics

Logs

To enable metrics gathering, Bleemeo agent needs to be installed with JMX enabled, see Java Metrics for setup details.

In addition Confluence need to expose JMX over a TCP port. To enable JMX you need to:

• Add option -Dcom.sun.management.jmxremote.port=3333 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false to the JVM. Default JIRA startup-script accept them from CATALINA_OPTS or JAVA_OPTS environment variable.

Warning: this will allow unauthenticated access. Make sure no untrusted access to this port is possible or you should setup authenticated JMX access.

Bleemeo agent should auto-detect the JMX port, if some auto-detected parameters are wrong, you can manually override them by adding the following to /etc/glouton/conf.d/99-local.conf:

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"

Agent gathers the following metrics:

Metric	Description
service_status	Status of JIRA
jira_jvm_gc	Number of garbage collection 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