Production Readiness in action

Engineers use the Engineering homepage as their personalized daily starting point. It provides a centralized view of key signals and tasks related to Production Readiness standards, including:

• Active work: See your open PRs, PRs assigned for review, active Jira tickets, and action items from Scorecards and Initiatives, ensuring you are aware of your responsibilities and can quickly address gaps that impact Production Readiness.

• On-call status: See current and upcoming on-call shifts, helping you stay prepared for incident response.

• Scorecards and Initiatives: See real-time progress toward Production Readiness standards.

• Shortcuts: Use direct links to quickly access your owned entities.

Review failing rules

When a Scorecard rule is failing, this information is surfaced to you in multiple ways:

• Scorecard rules that require your attention appear on the Engineering homepage.

• You can receive notifications via Slack, Microsoft Teams, or email when a Scorecard rule is failing.

  • Learn more about configuring notifications in the docs.

• You can review a Scorecard's progress in reports or by viewing the Scorecard in Cortex.

Remediate failing rules

When a service falls short of standards, there are different ways you can approach remediation:

• You can identify and troubleshoot trends in Scorecards, and consider scalable remediation efforts. Learn more in Review and evaluate Scorecards.

• You can configure a Workflow to automatically take action based on a Scorecard's score

• You can set up an Initiative to assign and track remediation tasks.

  • You can also automatically create issues in Jira, ClickUp, Azure DevOps, and GitHub based on Initiatives. After creating an issue config, Cortex will automatically create a parent issue for each entity with failing rules, and each failing rule will be created as a subtask. Learn more in Creating issues based on Initiatives.

After you add a verification period, you have the ability to query that verification period's results via CQL. This unlocks the ability to view verification status in reports and to create a Scorecard rule based on verification status, further automating Production Readiness checks.

For example, in a Scorecard you could define a CQL expression in a rule that checks for entities that have not been verified in over 30 days: (verifications(name="<name-of-verification>").verifications().all(verification => verification.status == "VERIFIED_CORRECT")) AND (verifications(name="<name-of-verification>").lastVerifiedAt().fromNow() > duration("PT-720"))

On the CQL reports page in your workspace, use the Entity Verification Report template to quickly set up a report that lists all entities that were labeled as "incorrect."