• Get started
  • Documentation

View team DevOps metrics

The team-level DevOps Metrics reports allow you to gauge your team's performance in terms of DevOps by providing relevant metrics and their trends. These metrics include the following primary metrics:

  • Deployment Frequency - How often is your team performing deployments per the time range selected in the filter.

  • Change Failure Ratio - The number of deployments made per number of failures where both incidents and alerts constitute as failures.

  • Meant Time To Respond - The average time taken by your team to resolve incidents.

DevOps metrics are more accurate and visualized better when you connect your Bitbucket workspaces to your Opsgenie account. This feature is currently only available for those who use Bitbucket as their VCS and deployment tool. Click here to find out more about connecting Bitbucket workspaces to Opsgenie.

Filters

  • Date - The time range over which DevOps metrics are tracked

  • Comparison Date - Time range over which previous DevOps performance is compared to current time range performance.

  • Deployment Environment - The system environment which applies to your deployments.

Looks

Deployment Frequency
The number of deployments made per week by the team.

Change Failure Ratio
The number of deployments over the number of failures where failures include incidents on services owned by the team.

Mean Time To Resolve Incidents
Indicates the mean time taken by the team in resolving incidents.

Deployment Frequency Trends
Two line graphs of deployment frequency vs time where one line is the total deployment frequency of the team and the other is the moving average calculated over 4 weeks.

Change Failure Trends
Two line graphs of change failure ratio vs time where one line is the change failure ratio across the organization and the other is the moving average of change failure ratio calculated over 4 weeks.

Time to resolve Trends
Two line graphs of the time to resolve vs time where one line is the mean time taken by the team to resolve incidents and the other is the moving average of the time to resolve calculated over 4 weeks.

Deployments
Single value shows the total number of deployments made by the team within the time period specified by the filter parameters selected.

Alerts
Single value shows the total number of alerts received by the team within the time period specified by the filter parameters selected.

Incidents
Single value shows the total number of Incidents incurred by the team within the time period specified by the filter parameters selected.

Deployment vs Failures
The graph juxtaposes the total number of deployments made over different weeks within the time range specified by the filter parameters, and the corresponding alerts and incidents within those weeks. Deployments are the total deployments made by the team and are represented by the bar charts. Incidents and Alerts are represented by the line graphs and similar to the deployments, relate to the total number of alerts and incidents within the specific week marked on the x-axis.

Deployment vs File Changes
The graph juxtaposes the total number of deployments made over different weeks within the time range specified by the filter parameters, and the number of files changed by those deployments. Deployments are the total deployments made by the team and are represented in the form of bar charts. File changes are represented in two statistical visuals with one line graph illustrating the max number of files changed within a deployment in the specific week marked on the x-axis, while the second line graph illustrates the corresponding median of file changes.

Service Health
The graph shows how healthy each service owned by the team is. This is measured by the percentage of time that the service was not undergoing an incident, where the time range is specified in the filter parameters.

Still need help?

The Atlassian Community is here for you.