Check whether the outcome improved
Replay steady and burst cases
Run the approved representative load shape at steady arrival and bounded burst concurrency in the same environment. Record latency distribution, statuses, timeouts, queue depth, resource intervals, and critical action completion. Keep the load duration and mix fixed so a change in traffic does not explain the result.
Check overload communication and safety
Exercise the system at and beyond the observed boundary only within the controlled test. Confirm rejection or delay is explicit, retry guidance has clear ownership, and partial writes cannot appear successful. Compare response bodies, status semantics, ordering, and idempotency evidence with the steady case.
Observe drain and return to normal
Continue measuring after arrival rate falls to baseline. Check queue age, in-flight work, errors, stale reads, duplicate records, and time to restore normal behavior. Re-run a critical action after recovery and verify it sees complete state rather than a leftover partial result.
What to carry forward
Classify burst behavior as improved, regressed, unchanged, or inconclusive with load, resource, user-action, and recovery evidence attached. It passes only when critical work remains correctly handled, overload behavior is understandable, queued work drains safely, and normal operation resumes without residual damage.
Keep the decision with the work.
Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.
Create an account See the product workflow