Changelog 2024.06

Monitoring Status Pages

We’re happy to announce that Loadster now includes free hosted status pages! If you’re using Loadster monitoring, you can set up a status page and share your site’s uptime and performance publicly with your customers or privately with your colleagues.

You can go to your monitoring dashboard to create a status page and select which of your monitors you want to display there. Depending on whether you want the status page to be public or private, you can generate a URL to share with anyone you want viewing it, or even map a custom subdomain like status.example.com.

You can learn more in Hosted Status Pages. Of course, you might want to set up Site & API Monitoring if you haven’t already, so there’s something to display on your status page.

Wildcard Cloud Regions

When you run extremely large load tests, there are occasions when the underlying cloud providers (AWS and GCP) lack capacity to run all the instances you’ll need in a specific region. Instead of trying different regions until you find regions with capacity, you can now select “Any Cloud Region” and Loadster will automatically find capacity for your test in whatever regions have it.

Capacity is rarely a concern in smaller load tests, so for those you can go on choosing whatever region you like, but the wildcard region is pretty helpful for running unusually big load tests.

Plan or Fuel Prompt

If you have a monthly or annual subscription but try to launch a test that exceeds your plan limits, Loadster will now prompt you to decide if you’d like to run the test with Loadster Fuel instead.

Assuming you have enough fuel, this can be a good way to cover the occasional test that exceeds your plan limits. Some of our customers use a monthly plan for routine testing and fall back on Loadster Fuel for the occasional extra large test, so if that fits your situation the process is now more straightforward.

Of course, if you don’t have a subscription and run all your tests with Loadster Fuel anyway, this doesn’t apply to you.

Other Improvements & Bug Fixes

• Scripts that are used for monitoring now display a badge for each monitor that uses the script (one-to-many).
• Implemented tag management for monitors, which previously only existed in Speedway monitoring.
• Fixed issues with extremely large load test reports failing to load.
• Fixed an occasional data issue with the iteration count coming a bit short at the end of the test.
• Removed a confusing but harmless navigation error that happened when duplicating a project.
• Removed a confusing but harmless prompt that happened when closing the modal after recording a script.
• Improved the 3D Secure verification flow for confirming a purchase on credit cards that support it.
• Got rid of a blank entry from the load test response time graph that appeared when using browser.waitForUrl(...).