Skip to main content

Success Rate

Drill into the reasons for why this replay did not match the expected results.

The errors dashboard gives you a view into all the calls that were replayed against the service, and how they compared to the traffic snapshot. There are 3 high level KPIs that are tracked:

  • Response Rate this helps confirm that the generator is able to send traffic to the service. If you have errors here it could be because the service was not ready or you have a misconfiguration in your clustuer.
  • Success Rate how did the responses compare with the traffic snapshot? These comparisons are made automatically based upon your configuration.
  • Responder Matches this is present if the responder was used during your traffic replay and is an indication if it was able to match the incoming calls.

Below that you can find a summary of failures by URL. Alternatively it may be interesting to understand what failure types happened in the environment regardless of URL.

Errors by URL

And finally there is a list of every single assertion that was performed automatically. You can click on any one of these to see the actual and expected results, with lines that did not match in red. The margin is also red for the parts of the body which do not match.

assertions diff

The Actual text for this assertion says "4/5 Lines Match" because the expected (captured) and actual (replayed) values differ. Each line of the response body, including delimiters like curly braces, are compared. Assertions can be configured, in the test config, to ignore fields that you don't want to affect body comparison.

assertions ignore

Ignored fields will still have red lines in the margin to indicate they are different, but the line itself is grey with the crossed eye icon to indicate that it was ignored. See the assertions reference for more information.

If your application has an unexpectedly low success rate, or displays other unusual behavior, reach out on the Speedscale Slack community or via email. We will be happy to walk through your specific use case. The Speedscale team is working on a configuration UI but for now we're happier to do the work for you than to have you stumble through this complex topic. If you're feeling adventurous, you can jump over to transforms to learn more.