BlazeMeter experienced a minor incident on July 10, 2023 affecting Performance Testing, lasting 11h 40m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jul 10, 2023, 03:52 PM UTC
We are aware of an issue with BlazeMeter when editing Performance tests and are presently investigating. We will post an update here as soon as we have more information.
- identified Jul 10, 2023, 04:44 PM UTC
The issue editing performance tests affects new and old tests alike, whenever attempting to change something on the test a message in the lower-right corner "Failed to update test" is displayed. This issue is only with JMX tests where the threads value in the JMX itself is not defined by a literal integer but is defined by value like a UDV or property. The issue has been identified and a fix is being implemented.
- identified Jul 10, 2023, 07:13 PM UTC
The issue editing performance tests affects new and old tests alike, whenever attempting to change something on the test a message in the lower-right corner "Failed to update test" is displayed. This issue is only with JMX tests where the threads value in the JMX itself is not defined by a literal integer but is defined by value like a UDV or property. Work on the fix for this issue is still ongoing at this time. We will provide another update once we have more information.
- monitoring Jul 10, 2023, 08:23 PM UTC
A fix has been deployed to Production and is working as we have observed so far. We are continuing to monitor the situation for any reoccurrences of the issue. We will provide another update soon.
- resolved Jul 11, 2023, 03:32 AM UTC
This incident has been resolved.