KR-qa-12 · file-based routing

API testing

k6 Signals for API SLO guardrails

Model steady-state, spikes, and soak patterns that talk to SLO dashboards your SREs already watch.

Evening cohort 5 evenings + office hours api-contract

₩980,000 informational tuition

See Money-Back Policy for eligibility windows.

k6 Signals for API SLO guardrails visual

Program narrative

Evening-friendly progression from single-route smoke to multi-step flows with think-time realism and honest thresholds.

What is included

  • Scenario templates for login-heavy APIs
  • Threshold language that matches Grafana boards
  • Soak plans that respect evening lab time windows
  • Tagging strategy for cost-aware cloud cost ops
  • Pair debugging when graphs lie
  • Handoff doc for on-call engineers
  • Optional extension into websocket fan-out

Outcomes you can evidence

  1. Ship three k6 scripts with tagged thresholds
  2. Draft an SLO alignment memo with graphs attached
  3. Run a soak without tripping employer spend alarms

FAQ

Cloud spend?

You run generators locally or in accounts your employer funds—we provide guardrails only.

Grafana required?

No, but examples export to Prometheus-compatible labels.

What is not covered?

Browser-level performance—this stays API and websocket edges.

Experience notes

“Threshold wording finally matched what our Grafana alerts expect—less midnight noise.”
Omar · SRE