- Connect Data: Ingest data and ensure ownership is assigned to your entities
- Improve: Review Eng Intelligence metrics to understand baseline metrics and take action when issues are surfaced
- Standardize: Configure a Scorecard to enforce and measure DORA standards
- Streamline: Use Cortex MCP to increase efficiency in incident response, leading to a decrease in MTTR
Use Cortex features to meet DORA standards
Expand the tiles below to learn about configuring Cortex features to help you meet DORA standards.Step 1: Ingest data and solve ownership 🔌
Step 1: Ingest data and solve ownership 🔌
Action Items:

Relevant integrations
Cortex calculates your DORA metrics by connecting directly to your delivery and incident management tools.To focus on DORA metric improvements, configure integrations in the following categories:- Version control: Azure DevOps, Bitbucket, GitHub, GitLab
- Cortex pulls cycle time and other PR-related metrics from version control integrations.
- Deploys: Add deploy data to Cortex via the deploys API
- This powers the metrics for deployment frequency and change failure rate.
- Incidents: PagerDuty
- Cortex pulls incident metrics, like incident frequency and MTTR, from PagerDuty.
- Custom metrics
- If you use internal tools, configure custom metrics to ensure you are tracking events that impact DORA metrics
- Project management: GitHub, Jira, Azure DevOps, ClickUp
- Track incidents and bugs, allowing you to collaborate with your team and speed up resolution times
- Code quality and security: Checkmarx, Codecov, Mend, Snyk, SonarQube, Veracode, Wiz
- Enforce code coverage, vulnerability scanning, and other quality measures
Step 2: Review Eng Intelligence baseline metrics 📈
Step 2: Review Eng Intelligence baseline metrics 📈
Action Items:
- Review Eng Intelligence metrics
- If you track DORA metrics through unsupported or internal systems, configure custom metrics

Configure custom metrics
If your organization already tracks DORA-related metrics or other delivery KPIs through unsupported tools or internal systems, you can send that data into Cortex as custom metrics.Step 3: Create a DORA Scorecard 📋
Step 3: Create a DORA Scorecard 📋
Action Item: Create a Scorecard for DORA
Step 2.1: Create the Scorecard and configure the basics
- On the Scorecards page in your workspace, click Create Scorecard.
-
On the
DORA Operational Readinesstemplate, click Use.

-
Configure basic settings, including the Scorecard’s name, unique identifier, description, and more.
- Learn about configuring the basic settings in the Creating a Scorecard documentation.
Step 2.2: Review and modify the rules
While Cortex’s template is based on DORA standards, you may want to adjust the rules based on how your organization prioritizes standards and requirements. You can reorder, delete, and edit rules, you can add more rules to a level, and you can assign more points to a rule to signify its importance.The Scorecard template contains rules that enforce increasingly higher DORA standards in each level, such as:- MTTR less than 12 hours in the “Established” level and less than 60 minutes in the “Elite” level
- Change failure rate less than 30% in the “Established” level and less than 10% in the “Elite” level
Step 4: Streamline processes via Cortex MCP 🤖
Step 4: Streamline processes via Cortex MCP 🤖
Action Item: Configure Cortex MCP
-
Real-time, structured answers: Ask questions like “Who is on call for backend-server?” or “Give me all the details for parser-service.” MCP fetches the data in real time from Cortex’s API, ensuring accurate and up-to-date information about service health, ownership, and operational readiness.

-
Actionable recommendations: MCP can suggest next steps or remediation ideas based on Scorecard and Initiative data, helping you identify and address gaps in incident response.
