简体中文界面。帖子、指南及政策正文保留原文；未对原文作自动翻译。
HanaArcher0361 · 2026年5月16日 18:10 UTC
Can you replay saved responses offline with a slow log destination? Measure receipt and processing separately.
15分It does. My replay keeps supplying responses, but processing stops inside the file write. Finally, something I can reproduce.
13分Move the replay's file writing behind a bounded queue and let a separate writer handle it. That should preserve both display progress and the diagnostic history.
3分@DavidAbbott0084 A bounded queue fills. You can't promise the whole diagnostic story survives. What happens when storage stays blocked?
4分You're right about my preservation claim. The design needs a deliberate overflow policy and visible dropped-sample counts so missing diagnostics aren't concealed.
3分Can routine samples be dropped but error summaries kept? I don't need endless identical status lines.
9分@HanaArcher0361 Yes, with explicit limits for both. Error summaries still need a failure path if storage remains unavailable.
13分My setup originally queued its overflow warning through the writer that was already full, so the warning disappeared along with the samples it was meant to explain.
-1分So where does that warning go? Another log sounds like the same problem twice
19分Expose a counter or health state directly in the application. Include it in exports when writing is possible again.
16分@DavidAbbott0084 I'll make logging health visible beside our monitor status. A moving display shouldn't quietly imply complete logs.
8分@HanaArcher0361 Are you displaying when the application observed the sample or when the writer saved it? A delayed writer makes those different events.
17分Written, currently. That's awkward. Our charts could make a disk pause look like a late robot response.
12分Record when the application receives the observation and measure the later write delay independently, making the chart's chosen time field explicit.
10分Could the controller still be late, though? The replay only proves the disk can cause it
10分The replay establishes that synchronous logging can stall this application. It doesn't establish the absence of communication delays in the real diagnostic session.
11分Right. I'll label this as the reproduced logging stall, not the explanation for every delay we've seen.
8分