Manage your SLOs

The SLO Workbench is the backbone of the platform. In this page you are able to manage existing SLOs, as well as configure new ones. The SLOs configured through this workbench serve as the backbone for all the other components of the Rely.io platform.
SLO Workbench
The main element of the SLO Workbench is the SLO monitoring list. In this list you can find all  the SLOs that Rely.io is actively monitoring. It provides detailed information about the state of each SLO allowing you to quickly understand how they're performing and help you to quickly identify problematic situations.
The left most columns of the table, display information that uniquely identify an SLO like its name and category. The columns at the center of the table display real time performance insights that give you a quick overview of how each SLO is behaving. The right most columns create a context for the SLO by displaying customizable tags and owner associated with it.
Each SLO element displays the following parameters:
Name: an unique, comprehensive name for the SLO. As a good rule of thumb, the name should reference the SLOs goal and what component of your application it is targetting.
Category: the SLO's category. This informs you about which performance area your SLOs are monitoring. Each category is represented by a specific icon. You can hover your mouse over the icon to see the textual definitoin of the category.
Time Window: the SLO's compliance window. This column tells you the size of the rolling window that is applied to your SLOs. All performance indicators are calculated based on data within this window.
Service Level: a chart previewing the performance of the service-level indicator over the last few datapoints, relative to the SLO's target. This chart is color coded according to the current state of the underlying SLI. Hovering along this chart displays each datapoint's value, as well as the SLO's target.
Error Budget: the amount of error budget the SLO has left until the end of its compliance window. Since SLO compliance windows are rolling windows that roll at the end of each day, this indicator displays the amount of error budget you have left until the end of current day. This amunt is displayed as a percentual number accompanied by a progress bar to help you visualize how much error budget you have left. Hovering your mouse over this field displays a tooltip providing an estimate of how many failed requests, or dowtime the SLO has left until it breaches its target and becomes non-compliant.
Depletion Forecast: the time left until the SLO’s error budget is fully depleted based on the recent error budget consumption rate.
Dimensions: a list of all the dimensions assigned to a given SLO. In most situations, this column will only explicitly display one or two dimensions depending on the available space. You can see all dimensions by hovering your mouse over this field.
Owner: the user within your organisation that is responsible for monitoring and maintaining the SLO.
Options: a button that provides quick access to different SLO related actions such as Edit and Delete.
Iterating over an SLO
The process of setting up and monitoring SLOs is an iterative one. It's very rare for every SLO to perfectly align with your business expectations and operational constraints at first try. SLOs require constant review and buy-in from both developer and leadership teams. There are few reasons for this, some of the most important ones being fast changing business requirements and evolving customer expectations. For any of these situations it might make sense to reajust your SLO targets, or even rethink the way you're assigning dimensions to your SLOs. 
To edit an SLO, first identify the one you want to work on, open the options menu by clicking in the three doted icon situated at the right most side of the SLO list and chose Edit. This will prompt a modal to appear that allows to edit specific SLO parameters. From there, you can edit your SLO's name, change its compliance window size, adjust its target or add/remove dimensions to it.
Edit SLO modal
When you adjust the size of an SLO's compliance window, or the SLO target, these changes will only take effect in future calculations. All previously calculated SLO indicators will remain unchanged.
We are currently working on improving this mechanism by introducing SLO versioning. This will ensure changes affect both the SLO's historical data and the SLO moving forward, while maintaining a repository of past SLO iterations.
Last modified 5mo ago