SLA Dashboard
The SLA Dashboard tracks contract compliance across freshness and quality expectations. Use it to see which active data contracts are meeting their service levels, which are at risk, which are breached, and how compliance is trending over time.
When To Use It
Use the SLA Dashboard to:
- Review SLA compliance for active data contracts in the current space.
- Compare freshness status, quality status, and overall status per contract.
- Spot at-risk contracts before they become breaches.
- Review recent breach history for governance or incident triage.
- Export a space-level CSV report for sharing or offline review.
- Check organization-level compliance trends when you are in organization view.
Open The Page
Navigate to Quality -> SLA. The page uses the current scope:
| Scope | What You See |
|---|---|
| Space view | KPI cards, compliance trend, contract SLA status table, recent breaches, and CSV export. |
| Organization view | Organization-level KPI cards and compliance trend across the organization's spaces. |
The date range control supports the last 7, 30, or 90 days. The selected range
is preserved in the URL with the days query parameter.
KPI Cards
The top cards summarize the selected scope:
| Card | Meaning |
|---|---|
| Total contracts | Active contracts evaluated for SLA compliance. |
| Meeting SLA | Contracts whose overall status is meeting expectations. |
| At risk | Contracts close to breaching at least one configured SLA. |
| Breached | Contracts that have breached freshness or quality expectations. |
| Compliance | Percentage of evaluated contracts currently meeting SLA. |
Compliance is calculated from contracts whose overall status is meeting SLA.
Status Meaning
SLA status is evaluated separately for freshness and quality, then combined into an overall status.
| Status | Meaning |
|---|---|
| Meeting | The contract is within its configured SLA threshold. |
| At risk | The contract is close to a breach threshold and should be watched. |
| Breached | The contract is outside its configured SLA threshold. |
| No SLA | That dimension has no configured threshold, so it does not drive the overall status. |
Freshness SLAs compare the time since the latest relevant quality execution against the contract's freshness threshold. If a freshness SLA exists but no execution can be found, the freshness status is treated as breached.
Quality SLAs compare product quality score against the contract's quality threshold. When a contract has both freshness and quality thresholds, the overall status uses the worst active status.
Compliance Trend
The compliance trend chart shows daily counts for contracts meeting SLA and contracts breached during the selected range. Use it to answer questions such as:
- Did a breach start today or has it been recurring?
- Did remediation improve compliance after a pipeline or threshold change?
- Are compliance issues isolated to one incident window or part of a trend?
If trend data is empty, the scope may have no active contracts, no SLA thresholds, or no evaluated check history yet.
Contract SLA Status
In space view, the contract table lists each evaluated contract.
| Column | Meaning |
|---|---|
| Product | Product covered by the contract. |
| Contract | Contract name. |
| Freshness | Freshness SLA status. |
| Quality | Quality SLA status. |
| Overall | Worst active status across freshness and quality. |
| Minutes since refresh | Time since the latest relevant quality execution, when available. |
| Quality score | Current product quality score, when available. |
Use this table to identify whether a breach is driven by stale data, quality score, or both. Then open the product, contract, or quality check that owns the underlying signal.
Recent Breaches
The breach timeline lists recent SLA breaches for the selected range. Each item shows the product, breach type, threshold, actual value, and time observed.
Use recent breaches during triage:
- Confirm whether the breach is freshness-related or quality-related.
- Open the product and review its quality checks and recent executions.
- Check the contract thresholds against current producer capability.
- Remediate the pipeline, source data, or quality issue.
- Re-run or wait for the next scheduled check so the SLA status can recover.
CSV Export
In space view, use Export CSV to download a compliance report. The report includes product and contract names, space slug, freshness status, quality status, overall status, minutes since refresh, freshness threshold, quality score, quality threshold, and last checked timestamp.
CSV export is intended for space-level review. Organization view shows summary and trend data, but does not expose the space-level status table or export button.
Troubleshooting
No active contracts are shown means the current space has no active data contracts with SLA settings, or you are viewing organization scope where the per-contract table is intentionally hidden.
A contract shows No SLA means the contract does not define that threshold. Add freshness or quality thresholds to the contract if the dimension should be monitored.
Freshness is breached with no minutes since refresh means a freshness SLA exists but Qarion could not find a relevant quality execution for the product. Run or schedule the product's checks.
Quality is No SLA or blank means the contract may not have a quality threshold, or the product does not have enough quality-check results to compute a score yet.
The CSV export is missing means you are likely in organization view. Switch to the relevant space before exporting.
Related Guides
- Data Contracts for creating contracts and setting SLA thresholds.
- Quality Execution History for investigating the check runs behind freshness and quality status.
- Quality Checks for configuring and running the checks that feed SLA evaluation.
- Quality Dashboard for broader quality health and product breakdowns.
- Continuous Monitoring for monitoring workflows that connect quality checks, alerts, and SLA response.