Files
jcoffey-dev 68f3d29979
ci / fork-checks (pull_request) Skipped
ci / build (pull_request) Skipped
github/ci (branch) GitHub Actions
ci / github (pull_request) Successful in 10m26s
Delivery time leaves out the planned hold on aggregate reports (#517)
Aggregate DMARC and TLS reports are queued with their first attempt at a
random time up to three hours later, so reports from every server don't
reach receivers at once. Delivery time was counted from when a message
was queued, so a report held for hours on purpose and sent on its first
try showed up as hours of delivery time: the console's delivery-time
graph spiked and its average read 18 minutes against 2 seconds per
attempt.

send_report now records the hold in the message's flags, in the top 14
bits (50-63), which no flag uses, and the delivery-completed event's
elapsed time counts from the end of the hold. That event feeds the
delivery-time histogram, the stored metric the dashboard and scheduled
reports read, and delivery history. The hold itself is unchanged.

Spare bits rather than a new field, so the stored queue format doesn't
change: a node that doesn't know them ignores them and measures as
before, and the console's flag list only reads the bits it knows.
Messages already queued carry no hold and are measured as before.

Reported on Discord (#inbuxa).

Fixes #517
2026-11-20 16:26:31 -07:00
..