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.

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

Linux
Windows

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

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

Monitoring Troubleshooting

See Troubleshoot a Service Check or Missing Metrics for what applies to every service: finding the address and port Glouton really uses, what each check message means, and how to read the collection error — which does not appear in the agent logs at the default level.

The Service Check is not OK

The check only opens the TCP port — it sends no command — so it fails when the port is wrong (Connection refused), when a firewall drops the packets (connection timed out after 10 seconds), or when the configured address cannot be parsed (Invalid TCP address). A green check proves the port is open, and nothing more.

Metrics are Missing

A passing check says nothing about the metrics: they are collected separately.

These metrics travel through JMX, which is a separate pipeline: Glouton writes /var/lib/jmxtrans/glouton-generated.json, jmxtrans connects to the JVM’s JMX port, and pushes the values back to Glouton. Every link has to be in place.

Check that the port is open and answers, from the machine where the agent runs. This only shows a JVM running on the host — for a containerized JVM, compare the address in discovery.txt with the ports the container itself listens on:

sudo ss -lntp | grep java

What you see	Cause	Fix
the `bleemeo-agent-jmx` package is missing	jmxtrans is not installed	`sudo apt-get install bleemeo-agent-jmx` (or `yum`) — see Java Monitoring with JMX
`discovery.txt` shows no JMX port for the service	No JMX port	Glouton reads it from the JVM command line (`-Dcom.sun.management.jmxremote.port`); if the JVM does not have it, set `jmx_port` in the service configuration
connection refused by the JVM	JMX authentication is enabled	Set `jmx_username` and `jmx_password`
jmxtrans connects, then times out	JMX answered with an RMI address jmxtrans cannot reach	The JVM must advertise the address `discovery.txt` shows for the service, with `-Djava.rmi.server.hostname`
nothing at all, for a JVM in a container	jmxtrans connects to the container address, not to a port published on the host	Publishing the port does not help. The JMX and RMI ports have to answer on the container address, and `-Djava.rmi.server.hostname` has to be that address