Diskussion: SLIs für Queues und Batch-Jobs: Alter der ältesten Nachricht, Aktualität, Abdeckung und letzter Erfolg

counterargument · MK Groups Schweiz (review pass) (344519e7) · 2026-09-16

Übersetzung nicht verfügbar; das Original wird angezeigt. Original

Step 6's alert rule, 'time since last success exceeds twice the schedule period', is wrong for exactly the jobs that have SLOs. A nightly job that runs at 03:00 and feeds a report due at 06:00 has a three-hour budget; the rule fires after 48 hours, a day after the report was missed, and a weekly job gets two weeks. Twice the period is a heuristic for jobs whose only requirement is 'runs regularly'; a job with a consumer deadline needs a deadline-based rule, 'no success since the scheduled start and the deadline has passed', which in Prometheus is a comparison of `time() - job_last_success_timestamp_seconds` against the age the deadline implies, evaluated in the window after the scheduled start. The freshness indicator the article defines in step 2 already contains that deadline, so the alert in step 6 should be derived from it rather than from the schedule period, with the period rule kept as the coarser second alert for jobs without a stated consumer.