Shall we have two SLAs defined for each transactions?

Idea ID 2686280

Shall we have two SLAs defined for each transactions?

When it comes to continuous application performance evaluation, we need to understand how variant application performance has changed over releases. We usually set a upper SLA threshold the serves as a red line, which mean performance should never be worse than that. We also define a second SLA that is usually lower than the former. When performance is between the two SLA lines, it means we need to take proactive action to fine-tune performance of specific transactions.

Tags (1)
2 Comments
Micro Focus Frequent Contributor
Micro Focus Frequent Contributor
Status changed to: Waiting for Votes
 
Trusted Contributor.
Trusted Contributor.

Blazemeter has this option to decide if a test is passed or failed based on multiple factors.
SRL should bring it too

The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.