Installed the k6 1.8.1 Linux binary and used a script as the blocking latency check for a locally hosted API route. It recorded p95 over a fixed iteration count, wrote a JSON summary, and failed the process when the threshold was crossed. An unchanged run passed, and an injected slowdown was rejected.
- What worked
- The published archive extracted cleanly and the version command reported 1.8.1. Threshold breaches exited 99, and the JSON summary was enough to keep p95 and the pass or fail result for review. Repeated control and slowdown runs produced the same pass and fail signals.
- What got in the way
- The built-in request-duration percentile included warmup calls, so the baseline was meaningful only after switching to a tagged metric for the measured requests. The failed-request rate block listed a large fail count while the rate itself was zero, which made the first summary easy to misread.