Defining Service Level Objectives
You manage Service Level Objectives, or SLOs, at the stream level. SLOs can be added to any Stream, new or old, and once added any Floods launched from that stream will be evaluated in real-time against them.
To create an SLO, create a new stream or edit an existing stream. Between Design and Launch you will also see SLOs.
The SLOs tab is where you define Service Level Objectives for your Stream.
Visiting this page will show the list of existing SLOs for that Stream and a button to create new SLOs.
A Stream with some Service Level Objective definitions.
You create an SLO by defining a set of one-or-more rules. Each rule must have a Measurement, Aggregation, Comparator and Target. If you wanted to set an SLO for response time maximum of 2 seconds, you would set the Measurement to
Response Time, Aggregation to Maximum, Comparator to <, and enter a target of 2000 ms.
Defining and individual Service Level Objective.
If you want more than one rule in this SLO, click the Plus button. You can add as many rules as you need.
Click here to add more rules to the Service Level Objective definition.
Each rule will be evaluated individually, and the SLO will be evaluated as a logical AND of all the rules. Hence, all must pass for the SLO to pass.
Management such as editing, or archiving SLOs also take place at the stream level. Each SLO is represented by a box. Clicking on the hamburger menu on the box will show options to Edit and Archive the SLO.
Editing and Archiving Service Level Objective definitions.
Edit is similar to SLO Creation, however the form will be pre-filled with the existing SLO rules.
Archive will remove the SLO from the stream. It will be kept around so that older Floods from this Stream still make sense, but will not apply to future Floods.
If you change SLOs for a stream, future Floods will run against the new SLOs, and old Floods will still display their results against the SLOs at the time of their running.