Monitor critical paths and SLAs with Vision
This feature is still being finalized by Development.
Vision shows you, at a glance, whether the work that matters is on track to finish on time. You group jobs by tag into cards and give each card a service-level agreement (SLA): an expected start or finish time. Vision then colors the card as the day progresses: on track, at risk, late, or failed.
On a busy night, "will the core processing finish before the business opens?" is hard to answer from a flat list of jobs. By the time a late-running critical path is noticed, the deadline is already at risk, and nobody has a single view of the day's commitments.
The two views
- Live: the day's board. Pick a Schedule date, and each card shows its current state, refreshing on a short interval. Cards are hierarchical: a group card rolls up its children, and you drill in one level at a time (with breadcrumbs to climb back out).
- Cards: the list of cards and how they're organized, where they're created and edited.
Reading a card
A card reflects the jobs its tag pattern matches for the selected date, in that card's environment. Each tile shows one status label:
| You see | It means |
|---|---|
| Late | An SLA has been missed. A warning mark beside Start or End shows which one |
| At risk | On current pace, an SLA will be missed (forecast). The warning mark shows which one |
| Failed / Partial failure | At least one job failed (partial = others are still waiting or running) |
| Waiting / In process / Finished | Where the card's jobs are overall, with no SLA missed or at risk and no failure |
| Unknown / No schedule date | Vision can't evaluate the card, because (for example) the card's environment isn't reachable, or no scheduled run matches the date |
When more than one applies, the label higher in this table wins — except Unknown and No schedule date, which replace all the others.
SLA times are compared in UTC, while a tile's Start and End times are in your local time.
Jump to the jobs behind a card
From a tag card on Live, use View jobs to open the runtime Operations → Job Instances view for that card's environment, already filtered to the card's tag and schedule date, so you go from "this path is late" straight to the jobs causing it.
- The Live view refreshes every 15 seconds, so a card can be a few seconds behind.
- Unknown usually points at the card's environment (not reachable / not registered), not at the jobs.
- Vision does not send alerts unless Continuous has turned on trigger processing for your organization; it is off by default. Otherwise a card's triggers are saved but never fire, so watch the Live view.
- Tag patterns are case-sensitive:
Nightly-*does not match a job taggednightly-core.
Related topics
- Vision (critical-path monitoring & SLAs) — full configuration reference and troubleshooting
- Monitor the daily run (Operator)
- Respond to a failed job (Operator)
- Monitor critical paths and SLAs with Vision (Build Outcome)