Measuring DevOps performance has always involved cobbling together mismatched data from disparate systems. But thanks to the new connection between Bitbucket and Opsgenie, we are happy to report that Opsgenie and Bitbucket customers can now measure deployment and incident response metrics from a single dashboard in Opsgenie.
The DevOps metrics report is powered by the same connection that makes it possible for teams to investigate incidents caused by deployment issues. This also means that you need to connect your Bitbucket Workspaces to Opsgenie before you can use the DevOps metrics report. If you need help connecting Bitbucket to Opsgenie, follow the steps we have outlined at the top of this page.
DevOps Metrics Report
To view the report go to Analytics > DevOps Metrics in your Opsgenie account. There are two different reports, one at the Global level which visualizes DevOps metrics across all of the teams within your Opsgenie account, and one at the Team level where you get a more granular view into the performance of each team.
The top half of the report visualizes trends in deployment frequency, change failure ratio, and mean time to resolve. Thanks to a deep connection with Bitbucket, these key DevOps Metrics are at your team’s fingertips. Use them to review performance, and take a proactive stance towards improving your DevOps processes.
What do the charts mean?
Deployment frequency - The number of deployments over the period of time selected in the filter versus the previous time period.
Change failure ratio - The number of deployments over the number of failures which generated an alert or incident.
Mean time to resolve incidents - Mean time to resolve incidents over the period of time selected in the filter.
Deployments vs Failures - Visualizes how deployment trends may correlate with the number of failures experienced in a timeframe.
Deployments vs File Changes - Depicts how the number of files changed differs according to the trend of deployments.
Service Health vs Team Reaction - Service Health shows the overall health of each team. This is calculated as the average percentage of time each service of a team was not experiencing an incident. Team Reaction is defined as the percentage of incidents a team successfully closed within 24 hours from their start time.
We plan to add more metrics to this report that leverage even deeper connections between all of Atlassian’s incident management tools. We also plan to support metrics from tools outside of Atlassian - so let us know in the comments below which tools we should integrate next.