From 17790d12b9dab24892778649a2367eca5f895855 Mon Sep 17 00:00:00 2001 From: clawbot Date: Mon, 26 Oct 2026 06:58:28 +0000 Subject: [PATCH] README.md: rework against the seventh review Say plainly that an interval change clears the history and the cleared samples still get reported. Model: fable-5-1 --- README.md | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/README.md b/README.md index 85f6d03..3f51cc2 100644 --- a/README.md +++ b/README.md @@ -143,11 +143,12 @@ fields: - `timestamp`: the time of the report Each report carries only the samples no earlier report has delivered. A sample -waits only as long as the history holds it: the last 100 rounds of each host. -The samples an interval change clears wait apart, the last 100 of each host, -until they are delivered. Nothing is sent while the page is paused. A report -with no answer after 30 seconds is abandoned, and its samples go in the next -one. So a server that stored them but answered late gets them twice. +waits as long as the history holds it: the last 100 rounds of each host. An +interval change clears the history. The cleared samples are kept, the last 100 +of each host, until a report delivers them. Nothing is sent while the page is +paused. A report with no answer after 30 seconds is abandoned, and its samples +go in the next one. So a server that stored them but answered late gets them +twice. A failed delivery is quiet, as on a static file host with no backend: one debug log line when deliveries start failing, one when they recover. The checks go on.