Skip to content

docs(adr-0025): record the watcher's measured tick delivery - #160

Merged
Fl0p merged 1 commit into
mainfrom
flo-1087-measured-tick-delivery
Oct 20, 2026
Merged

Fl0p merged 1 commit into
mainfrom
flo-1087-measured-tick-delivery

Conversation

@Fl0p

@Fl0p Fl0p commented Oct 20, 2026 •

Copy link
Copy Markdown
Contributor

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.

gh run list --repo Flopsstuff/cotel --workflow=health-probe.yml --event=schedule --limit 150

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 now
recorded 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

  • Documentation
    • Updated watcher performance metrics with observed cadence, detection timing, and maximum gap measurements.
    • Clarified that latency descriptions should reflect measured behavior rather than scheduled intervals.
    • Revised internal-LAN snapshot-worker estimates to reflect observed ticket volume.
    • Documented the continued requirement for one ticket per outage and both alert-limit settings.

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>
@coderabbitai

coderabbitai Bot commented Oct 20, 2026

Copy link
Copy Markdown

Review in Change Stack →

Note

Currently processing new changes in this PR. This may take a few minutes, please wait...

⚙️ Run configuration
  • Configuration used: defaults
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 1de5ed33-546d-4147-87bd-b3ce97ce0025
📥 Commits

Reviewing files that changed from the base of the PR and between 8c6e410 and 389a50e.

📒 Files selected for processing: 1
  • docs/decisions/0025-best-effort-ingest-watcher-in-actions.md
+----------------------------------------+
| Even Chuck Norris needs a code review. |
+----------------------------------------+
  \
   \   (\__/)
       (•ㅅ•)
       /   づ
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Commit to this branch
  • Create a new PR
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@Fl0p
Fl0p merged commit e69e6b7 into main Oct 20, 2026
8 of 9 checks passed
@Fl0p
Fl0p deleted the flo-1087-measured-tick-delivery branch October 20, 2026 04:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant