Nothing here
INC-2291 Checkout latency over its objective in eu-central
Checkout p99 latency
eu-central, one sample a minute
- Time to detect Within objective
- 6m 41s Objective is 10m
- Checkouts affected Rising
- 12,480 1,340 more than 30 minutes ago
- Error budget spent
- 38% 11% at the start of the week, 27 points since
- Actions still open
- 10 Three closed in the last hour
Workstream board
Drag a card, or use the arrows on it, to move one stage. Open a card for its detail.Use the arrows on a card to move it one stage. Open a card for its detail.
Bar on a card
Its length is how long the action has been open, out of the time since detection. Colour is the band that age falls in.
- Under 20 minutes
- 20 to 59 minutes
- An hour or more
Bar on a lane
The age of the lane’s oldest action that has not reached Mitigating. A short bar means the lane is moving.
Limit on a stage
The most actions the team wants in flight there. A move past it is allowed and flagged, so the work still lands.
Priya Raman moved FAULT-118 to Mitigating
Your board still shows it in Investigating. Their change is the one that saved.
Customer impact 0
Oldest before mitigating —
Nothing here
Nothing here
Nothing here
Platform 0
Oldest before mitigating —
Nothing here
Nothing here
Nothing here
Nothing here
Comms and stakeholders 0
Oldest before mitigating —
Nothing here
Nothing here
Nothing here
Nothing here
Design notes
How we built the Faultline board, and where it departs from the Atlassian design system.
- Shape of the page
- A board under a curve. Four columns of work, crossed by three teams, beneath the one chart that says how bad it is.
- What it leads with
- The latency line, four times over its objective and flat since the team shed traffic. The four figures beside it each carry a length, and the board answers the line in the next block.
- Spacing
- Atlassian’s own scale, unchanged: eight pixels inside a control, sixteen between components. A board is read at a glance, so the gaps do the work that rules would.
- The one bold decision
- Severity reads as length. Every bar is a duration drawn against the incident’s own clock. Bars sit on cards, on lanes and under figures. The eye ranks the work before it reads a word.
Where the colour comes from
Every colour, size and corner is Atlassian’s published set, taken from the system rather than sampled by eye. Light and dark come from the same set, and in dark the cards stand out from the columns by a lighter surface, not by a shadow.
Measured contrast
Card text on its card
14.34 : 1 light, 9.84 : 1 dark
The floor for text is 4.5.
The weakest bar on its card
4.51 : 1 light, 9.78 : 1 dark
The floor for a drawn mark is 3. Atlassian’s paler step of the same hue measures 2.47 on white, so the page does not use it.
Where the page departs from the system
- The page carries its own light and dark switch. Inside Jira the workspace owns the theme, but this page stands on its own.
- Atlassian keeps its own typeface for its own products, so the page falls back to the stack Atlassian names for everyone else.
- A column past its limit is flagged and not refused. In an incident the work has to land somewhere, and the board says what it cost.
- On a laptop the navigation is a rail of icons until it is asked for its labels, so the board keeps its width.
- On a phone the four columns become a switcher showing one stage at a time, an issue opens as a sheet from the foot of the screen, and a bar of three views replaces the side navigation.