Prometheus Exporter for Bitbucket exposes Bitbucket metrics as JVM and application statistics to Prometheus.
...
- Global controls the Prometheus server's global configuration.
- Rule_files specifies the location of any rules that you want the Prometheus server to load.
- Scrape_configs controls what resources Prometheus monitors.
To enable Prometheus Exporter for Bitbucket so that it collects metrics and pulls it into Prometheus:
Use the following scrape_configs:
Code Block title prometheus.yml scrape_configs: - job_name: 'bitbucket' scheme: https #change to http if don't you have https metrics_path: '/<your_bitbucket_context_path>/plugins/servlet/prometheus/metrics' static_configs: - targets: ['myhost:1990']For a complete specification of configuration options, see the Prometheus configuration documentation.
Select Prometheus Exporter for Bitbucket endpoint in the Prometheus Status >Targets page where all registered applications are listed, to get the Prometheus metrics.
<<<Update screenshot with Bitbucket Build any of the available dashboards with the selected metrics.
<<<Update screenshot with Bitbucket
Configuring a secret token (recommended)
...
- Log into your Bitbucket as Admin.
- Go to Administration and click Prometheus Exporter Settings. The Prometheus Exporter Settings page opens.
- Generate or create a Token. We recommend to use 128 length symbol.
Use generated or created secret token in the following scrape_configs in the prometheus.yml configuration file:
Code Block title prometheus.yml - job_name: 'bitbucket' scheme: https #change to http if don't you have https metrics_path: '/<your_bitbucket_context_path>/plugins/servlet/prometheus/metrics' params: token: ['1234567890'] # i'd reccomend use 128 symbol lenght long [A-Za-z0-9] static_configs: - targets: ['myhost:1990']
...