Recognises OLAs unable to support the SLA
Components in series whose composed availability is below the SLA.
Can AI do this?
Not settled yet The benchmark tested this, but the models' answers do not settle yet whether they master it. 0 of 4 models in the current benchmark master it.
| Model | Tier | Probability of mastery | Status |
|---|---|---|---|
| gemini-4-argon | Flagship | 74% | Not shown |
| gemini-3.5-flash-lite | Low cost | 76% | Not shown |
| gpt-6-luna | Low cost | 74% | Not shown |
| claude-haiku-5-5 | Low cost | 75% | Not shown |
Mastered means a probability of at least 90% that the model has this knobit, estimated from its graded answers. “Not shown” means the answers do not settle it either way. How the models are tested.
What it looks like in practice
Expected result: The defect named on the service target above its composed components, and its fix or the question for its owner
How it is assessed: Flags the deficient case and passes the acceptable one. Deficient: SL-001 99.95 % on OL-001, OL-002, OL-003 at 99.9 % each (composed 99.70 %) Acceptable: SLA at most 99.7 %, or components raised (or made redundant)
Also known as: OLAs that cannot support the SLA
Related knobits
Builds on
Usually followed by
All 13 knobits of Define SLAs and OLAs.
Source: Review checklist 06-slas-olas, row 4 (20000; ITIL)