no-mistakes(document): Dedupe cadence copies; registry remains authoritative
PR Pipeline — Authorize → Validate → Review → Merge / auth (pull_request) Successful in 8s
PR Pipeline — Authorize → Validate → Review → Merge / validate (pull_request) Successful in 2s
PR Pipeline — Authorize → Validate → Review → Merge / lint (pull_request) Successful in 3s
PR Pipeline — Authorize → Validate → Review → Merge / ai-review (pull_request) Successful in 3s
PR Pipeline — Authorize → Validate → Review → Merge / gate (pull_request) Successful in 1s

This commit is contained in:
root
2026-09-12 16:02:15 +00:00
parent bb17c2120f
commit 21f7b6171c
2 changed files with 9 additions and 4 deletions
+3 -2
View File
@@ -79,8 +79,9 @@ proxy queuing.
Send a real model name and use a real (probe-designated) key.
- Probe timeout: 30s. A probe that takes longer than 30s IS the alert —
report "backend slow (>30s)" rather than hanging.
- Probe cadence: at most hourly. The 6h litellm-health cron cadence is the
standard; sub-hourly synthetic traffic distorts latency baselines.
- Probe cadence: at most hourly. The litellm-health cron cadence (authoritative
trigger in contract-registry.yaml) is the standard; sub-hourly synthetic
traffic distorts latency baselines.
### 5. Batch/benchmark jobs — schedule away from 04:00-07:00 EDT and chunk