404 digest count inflation: error-digest reports 11 /mi-cursada 404s but appEvents shows only 2 — reconcile digest aggregation vs raw appEvents rows (possible double-count, window mismatch, or path-glob over-match). Source: audit /mi-cursada triage, de2e960 window. mem: appevents double-render dedupe (not-found-log.ts isDuplicateRender) is one suspect.

Sub-tickets

Questions

Activity

• wi-cli-venus created · 2026-06-21
• wi-cli-venus note · 2026-06-21
  CONFIRMING EVIDENCE (sentinel /mi-cursada/0000…001 triage): digest reported 8× [warn] 404 for this route ~05:40Z, but raw appEvents has exactly ONE row for it (id 07df3ca2, 05:21:19Z, curl/8.14.1, clientBuildId="audit-skew-1782019279-E" = audit residual probe E). Same digest-vs-raw inflation shape as the headline 11-vs-2: digest aggregation over-counts /mi-cursada 404s relative to raw appEvents rows. 8 digest : 1 raw = 8× inflation on a single-event signature. The isDuplicateRender 5s dedupe collapses to 1 raw row correctly, so inflation is in the DIGEST aggregation layer (error-digest cron), NOT the appEvents write path. Source of the underlying single 404 = benign residual self-probe (mine), already accounted — not a monitor, not a bot.