SLO FAQ
Is it possible to move SLOs between projects?
You can move SLOs between projects without losing collected data and calculations. It is available in both sloctl and the Nobl9 web application.
sloctl: runsloctl move slo, specifying the required SLO and the target project- Nobl9 web application: go to your required SLO details. Click more actions and select Move SLO.
Here, you can also copy the SLO.
Can I restore a deleted SLO?
Deletion is permanent. The SLO is removed from Nobl9 and must be re-created.
Is it possible to create an SLO already with historical data collected by the data source?
It is possible to include historical data collected by your data source before SLO creation. For this, create the SLO with Replay if the integration with your data source supports it.
If a composite SLO contains another composite SLO as a component, does the top-level composite SLO treat the child composite SLO as an additional, separate SLO? Does it look at the individual SLOs within the child composite SLO?
If a composite SLO contains another composite SLO as a component, the top-level composite SLO treats the child composite SLO as a single SLO component. It does not look into or evaluate the individual SLOs within the child composite SLO directly.
The design of composite SLOs allows them to treat their components uniformly, regardless of whether those components are regular SLOs or other composite SLOs. This means the computation at each level is based solely on the results of its direct components and does not traverse deeper into the hierarchy. In this way, you can construct complex, tiered structures where each level is calculated independently, feeding the results upwards.
Additionally:
- You can include both regular SLOs and composites within a new composite SLO.
- There is no requirement for a "balanced" tiering structure in the hierarchy. For instance, some paths may have more tiers than others, but their impact on the top-level composite is propagated through the intermediate tiers.
- You can influence the component contribution to its immediate parent composite by setting the component weight in the parent composite.
The top-level composite burn rate is only affected by the third-tier burn indirectly, as the third-tier burn impacts the second-tier burn, which in turn feeds into the top-level composite. This approach ensures that composite SLOs remain modular and focused on their immediate components, allowing for flexibility in their construction and interpretation.
Can I view sample queries for my data source?
You can find sample queries in the Sources > Creating SLOs section.
Select your data source from the list and refer to the Creating SLOs with section.
Can I restrict access to SLOs?
To set limits on SLOs, assign user roles with specific permissions regulating access to them at the project level.
Read more about project roles.
Can I share the link to my SLO?
- Go to Service Level Objectives.
- Click the required SLO to open its details.
- Copy a link (a URL) to the SLO in the address bar and share it as you need.
Which units are the error budget and burn rate measured in?
In Nobl9, error budgets are measured in percents. Additionally, we display them as time units to make them easier to comprehend.
Burn rates units are displayed as coefficients:
- A 1x burn rate means you will burn through (but not exceed) your error budget during your defined time window
- A burn rate below 1x over an entire time window means you will have an error budget remaining at the end
- A burn rate above 1x over an entire time window means you will exceed your error budget