Changelog 2023.10

2023.10

Trace Multi-Filtering

You can now filter traces on a live test or test report by multiple dimensions. For example, you can filter where the trace level is ERROR and where the message matches a certain substring.

Multi-dimension trace filtering interface

You can also toggle the match type for each filter between exact match and partial match.

Traces are useful for diagnosing problems with a load test or ensuring that the script was running as planned. Clicking on a trace in the table pops open more details such as the bot logs, full requests and responses, screenshots, resource waterfalls, and error details.

Other Improvements & Bug Fixes

  • Fixed a timezone issue in the activity log that sometimes caused events to appear on the wrong day in certain timezones.
  • Fixed a bug that sometimes prevented updating or deleting existing integrations.
  • Fixed a rare bug that caused slightly fewer bots to be launched than intended, due to a cluster rounding error.
  • Added an error message so it’s apparent when a WebSocket connection fails due to network problems, typically during script playback.
  • Updated the Slack integration to differentiate between Loadster and Speedway messages.
  • Upgraded Chrome browsers to address instability with certain sites.
  • Fixed a bug that caused a test’s Terminate button to be unclickable immediately after clicking the Stop button.

Further Reading

When you run a load test with hundreds or thousands of bots, the trace table can get pretty long. Multi-dimension filtering makes it possible to zero in on exactly the traces you care about – for example, finding all error traces for a specific URL pattern, or all traces from a particular bot group with response times above a threshold. This is especially helpful for understanding patterns in your test results rather than scrolling through everything manually.

Traces give you a window into what each bot actually experienced, which is often the key to figuring out whether a performance issue is on the server side, the script side, or somewhere in between.

For more on making sense of your test data, see analyzing test results and our guide on load testing best practices.

« Loadster Changelog