Project DORA Metrics API: Support "Time to restore service"
Release notes
The user should be able to use the API to query for "Time to restore service" data using an external tool.
Problem to solve
The DORA4 metrics are 4 key metrics that have become industry standard for measuring DevOps success. In 14.9, the Manage stage will be adding API support for the final two metrics. Support via API allows external tools to poll GitLab and export the data. The third metrics is Time to restore a service which is measured as median time to close production incidents.
As an executive investing in DevOps, I want to see my ROI. I want to see an improvement in the time MRs to get merged of my dev team. This will most likely drive the KPIs of my team.
As a developer leader I want to see that the team is improving by measuring the Time to restore service and comparing it over time (over sprints)
I want to import the data from GitLab into an external monitoring tool, so I need API support to poll the data.
Intended users
User experience goal
The user should be able to use the API to present the Time to restore service data in an external tool.
Proposal
The project-level DORA key metrics API should accept a metric parameter value of time_to_restore_service. In that case it should return "Time to restore service" values, calculated as the median duration in days (from open to close) of all Incident records closed in the given time period. (See the key metrics definitions for more details on calculation.)
Out of scope
In the future we will add group level and instance level support.
Permissions and Security
Documentation
Availability & Testing
What does success look like, and how can we measure that?
What is the type of buyer?
Is this a cross-stage feature?
Links / references
This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.