Say plainly that an interval change clears the history and the cleared samples still get reported. Model: fable-5-1
This commit is contained in:
@@ -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.
|
||||
|
||||
Reference in New Issue
Block a user