CASC Score (Quality Score)
The CASC score (displayed in the UI as Quality Score) is a single number between 0 and 9.99 that summarises the health of a monitor or project based on its recent pass/fail history, latency trends, and conformance results.
What the number means
| Range | Meaning |
|---|---|
| 8.00–9.99 | Healthy — meeting all defined SLOs |
| 5.00–7.99 | Degraded — some failures or latency spikes |
| 0–4.99 | Critical — significant failure rate or SLO breach |
A score above 7.99 is the default threshold for a "passing" project. You can customise SLO thresholds in Project Conformance settings.
What feeds into the score
The score is computed from three weighted signals:
- Pass/fail rate — the primary driver; a flat failure run immediately depresses the score
- Latency variance — consistent high latency against your CASC threshold lowers the score even if responses succeed
- Conformance compliance — schema and security profile violations contribute a conformance penalty
The exact weighting is proprietary, but the dominant factor is always the pass/fail rate over a rolling window.
Quality Score vs CASC Score
The CASC Score is the technical name; the Quality Score is the name shown in the UI. They refer to the same value. Older documentation and API responses may use casc_score in JSON fields.
Where to find it
- Project overview — aggregate score across all monitors in the project
- Individual monitor — score for that monitor's recent run history
- Quality Analytics — detailed breakdown of score drivers
See also
- SLA Model — how CASC scores map to SLOs
- Conformance Explained — conformance signals that affect the score
- Quality Analytics guide — working with the score in practice