Bitbucket

Auto-Detection

Built-in Metrics

Bleemeo monitors Bitbucket through automatic service detection and JMX metrics collection for Git repository performance.

Auto-Detection

Glouton automatically detects Bitbucket instances running on the system.

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

Bitbucket must also expose JMX over a TCP port. Follow the Enabling JMX counters for performance monitoring guide on Atlassian documentation.

Summary for unauthenticated access:

• Add -Dcom.sun.management.jmxremote.port=3333 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false to the JVM. The default Bitbucket startup script accepts these from JMX_OPTS or JAVA_OPTS environment variables.
• Add jmx.enable=true to $BITBUCKET_HOME/shared/bitbucket.properties.

Caution

This allows unauthenticated access. Ensure no untrusted access to this port is possible, or set up authenticated JMX access.

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

Linux

sudo tee /etc/glouton/conf.d/99-bitbucket.conf > /dev/null << 'EOF'
service:
  # For a Bitbucket running outside a container
  - type: "bitbucket"
    address: "127.0.0.1"
    port: 7990
    jmx_port: 3333
    jmx_username: "monitorRole" # by default, no authentication is done
    jmx_password: "secret"

  # For an additional Bitbucket running outside a container
  - type: "bitbucket"
    instance: "NAME_ASSOCIATED_WITH_YOUR_ADDITIONAL_SERVICE"
    address: "127.0.0.1"
    port: 7991
    jmx_port: 3334
    jmx_username: "monitorRole" # by default, no authentication is done
    jmx_password: "secret"

  # For a Bitbucket running in a Docker container
  - type: "bitbucket"
    instance: "CONTAINER_NAME"
    address: "172.17.0.2"
    port: 7990
    jmx_port: 3333
    jmx_username: "monitorRole" # by default, no authentication is done
    jmx_password: "secret"
EOF

Windows

Create or edit C:\ProgramData\glouton\conf.d\99-bitbucket.conf:

service:
  # For a Bitbucket running outside a container
  - type: "bitbucket"
    address: "127.0.0.1"
    port: 7990
    jmx_port: 3333
    jmx_username: "monitorRole" # by default, no authentication is done
    jmx_password: "secret"

  # For an additional Bitbucket running outside a container
  - type: "bitbucket"
    instance: "NAME_ASSOCIATED_WITH_YOUR_ADDITIONAL_SERVICE"
    address: "127.0.0.1"
    port: 7991
    jmx_port: 3334
    jmx_username: "monitorRole" # by default, no authentication is done
    jmx_password: "secret"

  # For a Bitbucket running in a Docker container
  - type: "bitbucket"
    instance: "CONTAINER_NAME"
    address: "172.17.0.2"
    port: 7990
    jmx_port: 3333
    jmx_username: "monitorRole" # by default, no authentication is done
    jmx_password: "secret"

Glouton automatically detects configuration changes.

Built-in Metrics

Metric	Description
service_status	Status of Bitbucket
bitbucket_events	Number of events per second
bitbucket_io_tasks	Number of events per second
bitbucket_jvm_gc	Number of garbage collections per second
bitbucket_jvm_gc_utilization	Garbage collection utilization in percent
bitbucket_jvm_heap_used	Heap memory used in bytes
bitbucket_jvm_non_heap_used	Non-heap memory used in bytes
bitbucket_pulls	Number of pulls per second
bitbucket_pushes	Number of pushes per second
bitbucket_queued_events	Number of events queued
bitbucket_queued_scm_clients	Number of SCM clients queued
bitbucket_queued_scm_commands	Number of SCM commands queued
bitbucket_request_time	Average time of request in seconds
bitbucket_requests	Number of requests per second
bitbucket_ssh_connections	Number of SSH connections per second
bitbucket_tasks	Number of scheduled tasks per second