Repository navigation
docs(adr-0025): record the watcher's measured tick delivery - #160
Merged
Merged
Conversation
The first full day of the ingest watcher delivered 4 scheduled runs against 91 expected (4.4%), with gaps of 6.4, 4.2 and 3.0 hours. Counting only from the first tick gives the same rate, so this is steady-state drop and not registration lag. The decision stands: the acceptance bar is same-day detection and a 6.4 hour worst case clears it. What changes is the latency a reader infers from the cron expression, so the measured cadence is now recorded next to it. Also corrects the nominal "96 tickets a day" figure in the blind-half bullet, which is about 24 times the real rate. The dedup pair is still required; the requirement is one ticket per outage, not a tolerable count of them. Co-Authored-By: Daedalus <daedalus@agents.flopbut.local> Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
Note Currently processing new changes in this PR. This may take a few minutes, please wait... ⚙️ Run configuration
📒 Files selected for processing: 1
✨ Finishing Touches
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The ingest watcher has now run for a full day, so ADR-0025's latency claim can
be replaced with a measurement instead of an estimate.
Measured 2026-10-19 05:30Z to 2026-10-20 04:06Z: 4 scheduled runs against 91
expected, 4.4%. Ticks at 11:07, 17:28, 21:42 and 00:42Z; gaps of 6.4 h, 4.2 h and
3.0 h. Counting only from the first tick gives 3 of 67, the same rate, so this is
steady-state drop rather than the registration lag a fresh cron can show.
This does not reopen the decision. The bar the watcher was built against is
same-day detection, after six days of blindness was the original failure. A 6.4 h
worst case clears it. What the measurement does invalidate is the latency a reader
infers from
*/15, so the real cadence - roughly one look every 5.7 hours - is nowrecorded beside it.
Second change: the blind-half bullet claimed a naive pager would mint "96 a day for
one outage". That is the nominal figure and about 24x the real one; at measured
delivery it is nearer 4 a day. The dedup pair is still required, but on the grounds
that the requirement is one ticket per outage rather than on a scare number.
Docs only, no behaviour change.
🤖 Generated with Claude Code
Summary by CodeRabbit