How-to Guide
Interpret reliability reports
Read reports metrics for operational and release decisions.
Objective
Read reports metrics for operational and release decisions.
Prerequisites
- Runs exist
- Reports access
Procedure
Open Reports
Navigate to Operate → Reports.
Navigation: Operate → Runs, Reports, or Schedules. Filter by project in large tenants to reduce noise.
Verification: Confirm organization and team context in the Console header before making changes.
Review key metrics
Analyze pass rates, trends, and failure categories.
Navigation: Operate → Runs, Reports, or Schedules. Filter by project in large tenants to reduce noise.
Verification: Note project, run, or agent IDs if you may need support escalation.
Cross-reference Test Health
Link report findings to flakiness and clusters.
Navigation: Operate → Runs, Reports, or Schedules. Filter by project in large tenants to reduce noise.
Verification: Confirm UI state matches your runbook. Retry once on transient errors before opening a ticket.
Verification checklist
- Confirm expected UI state or API response after each critical step
- Document run ID, project ID, or agent ID for support escalation if needed
- Notify stakeholders if the workflow affects release gates or production validation
Expected result
Team interprets reliability posture from report data.
Was this page helpful?