--- title: OctoPerf 11.6 - Automatic SLAs and other quality of life features url: https://blog.octoperf.com/octoperf-116---automatic-slas-and-other-quality-of-life-features/ date: '2025-09-29' authors: - gbetaillouloux categories: - Innovation tags: - Analysis - SLA - Response Time - Errors - JMeter - Correlation description: OctoPerf 11.6 is available, with new automatic SLAs, improved administration for enterprise customers and increased usability with many small quality of life features --- # OctoPerf 11.6 - Automatic SLAs and other quality of life features ## Article Summary OctoPerf 11.6 focuses on usability and analysis quality with automatic SLAs applied to all default reports. JMeter is updated to 5.2.1 with safer cache behavior enabled by default. Correlation rules can now be reused across projects and workspaces, simplifying script maintenance. Enterprise administration gains stronger workspace visibility and control. Reporting improves with clearer SLA indicators and a test configuration summary for easier analysis. ## Table of Contents - [JMeter 5.2.1](#jmeter-521) - [Counter variable](#counter-variable) - [Enterprise edition Admin](#enterprise-edition-admin) - [Correlation rules transfer](#correlation-rules-transfer) - [Automatic SLAs](#automatic-slas) - [Test configuration summary](#test-configuration-summary) - [Full changelog](#full-changelog) - [Conclusion](#conclusion) - [Introduction](#introduction) ## Introduction ## JMeter 5.2.1 In december, we updated OctoPerf to use the latest [JMeter](https://jmeter.apache.org/) version. Although, as a minor version, it doesn't bring a lot of [new features](https://jmeter.apache.org/changes.html), it is always better to stay up to date with the latest bugfixes. We had to implement a small change in OctoPerf because JMeter now properly enforces the cache control headers in every situation. To avoid any confusion, **cache control headers have now been disabled by default** in OctoPerf: ![Cache control](https://blog.octoperf.com/img/blog/octoperf-11-6/cache-control.png "Cache control") Simply because every script using a loop or calling the same page several times could be impacted by this change otherwise. You are welcome to activate them if required anyway. ## Counter variable We decided to add the [counter variable](https://api.octoperf.com/doc/design/edit-virtual-user/configuration/variables/counter/) to our Variables menu: ![Counter](https://blog.octoperf.com/img/blog/octoperf-11-6/counter.png "Counter") This way, counter variables that are outside-of your threadgroups would be imported anyway. And you can still configure them from inside OctoPerf. And at the same time, **people using OctoPerf to design their scripts will benefit from this functionality** as well. ## Enterprise edition Admin When using your own OctoPerf enterprise edition, the platform admin can access a [dedicated menu to manage users and agents](https://api.octoperf.com/doc/administration/). Creating an admin account has recently been made easier since you can just [declare the admin e-mail](https://api.octoperf.com/doc/on-premise-infra/configuration/#user-management) in the configuration files. For that occasion we've also added a [workspace management](https://api.octoperf.com/doc/administration/#workspace) tab to our admin UI: ![Workspace](https://blog.octoperf.com/img/blog/octoperf-11-6/workspace.png "Workspace") This way the platform administrator can see and manage all the [workspaces](https://api.octoperf.com/doc/workspace/) created by every user on the platform. With this feature the admin console **allows the administrator to properly manage everything in real time** without having to know the other users credentials. ## Correlation rules transfer [Correlation rules](https://api.octoperf.com/doc/design/edit-virtual-user/configuration/auto-correlation/), are the perfect way to handle dynamic parameters automatically. The only issue so far was that they were local to each project. This is now fixed, because you can [copy/paste correlation rules](https://api.octoperf.com/doc/design/edit-virtual-user/configuration/auto-correlation/#copypaste-between-projects) accross your projects now: ![Copy correlation rule](https://blog.octoperf.com/img/blog/octoperf-11-6/copy-correlation-rule.png "Copy correlation rule") This works in a similar fashion to the [action tree copy/paste](https://api.octoperf.com/doc/design/edit-virtual-user/#copypaste-actions/design/edit-virtual-user/#copypaste-actions). And of course they can be copied in different [projects](https://api.octoperf.com/doc/project/) or different [workspaces](https://api.octoperf.com/doc/workspace/). ## Automatic SLAs The thing with [SLA profiles](https://api.octoperf.com/doc/design/edit-virtual-user/configuration/sla-profiles/) is that very few users actually use them. So we've made the decision that **all our default reports will now have SLAs**. They are based on a couple of simple criterias, first we use the [APDEX configuration](https://api.octoperf.com/doc/analysis/edit-bench-report/metrics-selection/) for response times SLA: ![APDEX SLA](https://blog.octoperf.com/img/blog/octoperf-11-6/apdex-sla.png "APDEX SLA") For percentage of error and response size we use the [report configuration screen](https://api.octoperf.com/doc/analysis/edit-bench-report/configuration/#graphs): ![Error rate SLA](https://blog.octoperf.com/img/blog/octoperf-11-6/error-rate-sla.png "Error rate SLA") And the final result is visible in different report items, as **a colored square next to each relevant metric**: ![Auto SLA](https://blog.octoperf.com/img/blog/octoperf-11-6/auto-sla.png "Auto SLA") As you've seen, **these SLAs can be configured to the value you want**, even during/after the test. And at least this way you get a first quick overview of what's wrong during your tests. ## Test configuration summary Sometimes when a test was run a long time ago **it was hard to figure out which configuration was used** on the runtime screen. Because of that analysis and comparison may not be so easy. That's why our [summary report item](https://api.octoperf.com/doc/analysis/edit-bench-report/report-items/summary/) has been upgraded to display the test configuration: ![Test configuration](https://blog.octoperf.com/img/blog/octoperf-11-6/test-config.png "Test configuration") This **works with any test launched in OctoPerf**, even before this update. ## Full changelog For the complete list of fixed bugs, please refer to [11.6 Release Notes](https://api.octoperf.com/doc/release-notes/#1160-19th-february-2020). ## Conclusion You can probably tell that there are less major features than usual in these last months, that's because **we've been working with our customers to improve quality of life** in many different aspects of OctoPerf. Many of them we didn't even cover here as they are very small. For instance, did you notice that we've added `Apply` buttons to all the design screen windows? Well a lot of people were confused because they were not sure their changes were properly saved. The `Apply` buttons basically close the window, but this way it is less confusing for a newcomer. This is the kind of small but important features we keep implementing on a daily basis to make OctoPerf easier to use. In any case, we hope you like the new features and as usual **we're waiting for your feedbacks**.