Changelog 2024.07

Tracing On Demand

Any bot in a load test can now take a trace “on demand” at any point in your script. Traces make it easier to tell what the bot is seeing and doing, and are useful for troubleshooting errors in a test or as a sanity check to make sure your scripts and site are behaving as expected.

To request an on-demand trace in a load test, simply call bot.trace() in a Code Block. The trace will show up as an INFO trace in the Traces section of the test report. On-demand tracing is only necessary to get more information about what other bots are doing and seeing, subject to the overall limits on traces per bot group or per test.

Loadster automatically takes ERROR traces in a load test whenever any bot detects an error, and INFO traces after every step by the first bot in each bot group (“Bot 0”).

Monitoring Improvements

If your monitors have detected a problem and opened an incident, and then you disable that monitor while the incident is open, the incident will now be closed and you’ll no longer receive repeat notifications. Previously, if an incident was open it would remain open even if you disabled the associated monitor.

We’ve also updated the weekly monitoring summary email that you receive every week if you have monitors enabled. Among other things, the email now includes a status timeline for each monitor, so you can see at a glance which time periods during the week the monitor had a particular status (passing, failing, misconfigured, etc).

Also, you’ll now receive email notifications if your monitors have a misconfiguration or get throttled by plan or fuel limits that prevent them from running. These are separate from the monitor failure emails, and are intended to let you know the monitor is not functioning correctly.

Last of all, the process of creating your first monitor in Loadster is now a bit friendlier.

Other Improvements & Bug Fixes

• Added instant feedback when an unsupported phone number country code is entered on the Account screen.
• Modified the Recent Tests dashboard section to include tests that are in the process of launching.
• Fixed an engine memory issue triggered by very large loops in code blocks.
• Fixed a minor issue with jumping to a specific monitor cycle in a monitor’s history.