From the GoReplay team

GoReplay reproduces production bugs. Proof catches them before production.

See Proof
GoReplay Logo

GoReplay planning tool

Build a useful load-test plan

Choose the question your test should answer, describe the workload, and export a checklist with a bounded replay example.

Start with measurements, then choose the workload

Daily users and concurrent users do not tell you requests per second. Use a measured request rate for the endpoint set and time window you plan to test, or leave it blank and include measurement in your plan.

A replay multiplier changes the gaps between recorded requests. Verify the rate that reaches your target, then compare latency, errors and resource use with your own acceptance criteria.

Your inputs and generated plan stay in this browser. This tool does not run commands or send test traffic. Copy and download are local actions.

Compare load-test types or review the GoReplay load-testing guide.

Describe one test stage

Stress, spike and capacity plans describe additional stages to schedule; one command does not create the whole pattern.

Requests per second for the traffic you intend to replay. Leave blank if you still need to measure it.

Choose a finite duration for your test objective. The starting value is not a recommended standard.

1 = original timing; 2 = 200% speed. Use at most two decimal places. This does not guarantee a target RPS.

Use your team’s service target. There is no default latency threshold.

A team-defined value from 0 to 100. Decide which responses and timeouts count as errors.

Prepare your capture and target

Talk to the GoReplay team

Describe what you want to capture or replay, your deployment, and any PRO requirements. Or email [email protected].

Google Forms will display your submission confirmation. Please leave out credentials and production request data.