Files
worldmonitor/scripts
Elie Habib 8f8213605f docs(brief-quality): correct help text — cap_truncation has no fallback estimate (#3393)
Greptile P3 follow-up on PR #3390 (already merged): the help comment
described cap_truncation_rate as "computed from production drop logs
if supplied via stdin, else estimated as max(0, in - 16)/in from
replay record counts" — but:

1. The "16" was stale (post PR #3389, cap default is 12).
2. The fallback estimate was never implemented. cap_truncation only
   appears when --drop-lines-stdin is passed.

Updated the comment to match what the code actually does: cap
metric is omitted entirely without stdin input. No fallback estimate
because replay records don't capture the post-cap output count, so
any derived value would be misleading.
2026-04-25 13:47:53 +04:00
..