For DeployBeat on Jira Cloud.
DeployBeat turns the Git, CI and incident events you already produce into the four DORA metrics, inside Jira. Your servers push events out over HTTPS — there is no VPN, no inbound port and no agent to install.
Install DeployBeat from the Atlassian Marketplace. It adds two pages to Jira:
The first time you open the app it asks for a link code. Paste the code you received when your DeployBeat installation was provisioned and select Link site. This ties your Jira site to your installation and only needs to be done once. A site can be linked to a single installation.
Point a webhook from each system at your installation endpoint. Replace {id} with your installation id; the secret is the one issued with your installation.
| System | Endpoint on api.deploybeat.com | Authentication |
|---|---|---|
| GitLab (self-hosted or cloud) | POST /webhooks/gitlab/{id} | X-Gitlab-Token |
| GitHub / GitHub Enterprise | POST /webhooks/github/{id} | HMAC X-Hub-Signature-256 |
| Bitbucket Data Center | POST /webhooks/bitbucket/{id} | HMAC X-Hub-Signature |
| Bitbucket Cloud | POST /webhooks/bitbucket-cloud/{id} | HMAC X-Hub-Signature |
| Gitea / Forgejo | POST /webhooks/gitea/{id} | HMAC X-Gitea-Signature |
| Azure DevOps (Repos and Pipelines) | POST /webhooks/azuredevops/{id} | Basic or Bearer |
| Jenkins | POST /webhooks/jenkins/{id} | Bearer token |
| Argo CD | POST /webhooks/argocd/{id} | Bearer token |
| PagerDuty | POST /webhooks/pagerduty/{id} | HMAC X-PagerDuty-Signature |
| Prometheus Alertmanager | POST /webhooks/alertmanager/{id} | Bearer token |
Events are idempotent: replaying a webhook does not double-count a deployment.
DeployBeat links commits to deployments through the issue key in the branch name, commit message or pull request title. Besides Jira it understands Linear (ENG-123) and, for Azure Boards and GitHub Issues, numeric references such as #123 mapped to a prefix you configure.
| Metric | How it is computed |
|---|---|
| Deployment frequency | Distinct production deployments in the window. |
| Lead time for changes | Median time from the first commit on an issue to the production deployment. |
| Change failure rate | With an incident source connected: deployments followed by an incident. Otherwise: failed deployments over total. |
| Time to restore | With an incident source: median from incident open to resolved. Otherwise: median from the failing deployment to the one that restores service. |
Each metric carries its Elite / High / Medium / Low band, following dora.dev. Connecting PagerDuty or Alertmanager is what turns change failure rate and time to restore from an inference into a measurement.
The app requests read:jira-work only and never writes to Jira. On a project page it verifies you can open that project before showing anything. On the global page it first resolves which projects you can open and reports on those only, so you never see metrics for a project you could not otherwise access.
Uninstalling unlinks your Jira site and erases that installation's event data from the DeployBeat backend. See the Privacy Policy and DPA.
Questions about setup or metrics: hello@deploybeat.com. Security reports: security@deploybeat.com (see the Security Overview). Privacy requests: privacy@deploybeat.com.