Skip to main content

# SLOs

#### If I delete an SLO, can I get it back?​

• Deletions are permanent. The SLO is removed from Nobl9 and must be re-created.

#### Why do I see irrelevant data for my SLOs?​

• You may see irrelevant historical data for your SLO if you have deleted an SLO and created a new one using the same Project, Name, and Objectives. The newly created SLO is measured from scratch but until the data for the new SLO is collected, the Service Health dashboard shows the status of the deleted SLO.

#### How long does it take for metrics data to get into Nobl9?​

• Nobl9 starts to display data points as soon as metrics data is received and processed. As soon as Nobl9 starts gathering the metrics data, users can see the first data point on each graph in the grid view and in the details view.
• Note: This applies to the Service Level Indicator, Reliability Burn Down, and Error Budget Burn Rate graphs.

#### Is there a way to sort the dashboards by SLO type, or by Projects?​

• In the Grid View, you can use the label functionality to sort the page and tie different SLOs and projects together. You can then bookmark the link that is created and use it to always come back to that set of SLOs. For example, you might want to bookmark a link that allows you to easily view all the SLOs in your instance with the label latency.

#### Is there a way to create separate Dashboards for different projects?​

• Currently, there is no way to create separate dashboards for different projects. However, you can use a label to group the SLOs for a given project together and sort them by that.

#### Could I associate an Agent with multiple Projects?​

• An Agent can only be associated with one Project when it’s created. However, when you create an SLO, you can use the Agent from any project. For more details, refer to the Nobl9 Agent | Nobl9 Documentation.

#### Is it possible to use the same Client ID and Secret for multiple Agents?​

• Client IDs and Secrets must be unique for each Agent.

#### Is there a historical metrics import option or does metrics collection always start from the SLO creation time?​

• Yes, you can retrieve your historical metrics while creating a new SLO with an enabled Replay feature. For more details, check Replay documentation

#### Is it possible to update an SLO to move it to another Service or Project?​

• Our objects are managed in a declarative manner, similar to Kubernetes. As such, making changes to certain specifications creates a new SLO-type object.
• If you update an SLO using the sloctl binary and try to change the project with the sloctl apply command, the SLO is duplicated in the new project.
• You can use sloctl to move SLOs to another service as long as they belong to the same project.

#### Is it possible to move SLOs into the new Projects without losing historical data?​

• You can't move your existing SLOs between projects without losing your SLO's historical data. For more information, refer to the Editing SLOs guide.

#### What happens when I edit an SLO?​

• Note that editing an SLO and updating some of its settings, such as:
• Target
• Threshold
• Error budget calculation method
• Time window
• results in losing your historical metrics data. Any changes in the above settings will reset the error budget of your SLO and remove the budget history.
• For more information, refer to the Editing SLOs | Nobl9 Documentation.

#### Are there sample queries for different SLOs?​

• Sample queries can be found in the Sources | Nobl9 Documentation. Select the appropriate data source from the list on the left. Sample queries can be found under the Creating SLOs in the UI heading.

#### I've stopped receiving data for all SLOs. What can I do?​

• First, try to restart your Agent. If this doesn’t work, contact our support team.

#### Can I limit the number of SLOs per project or by a Team or a User?​

• Go to the Service Level Objectives page and click the SLO to view its details. You'll get a deep link in your browser’s address bar that can be copied and shared. A deep link is the URL in your browser. Currently, the deep linking feature is available from the following pages:
• Grid view
• SLO details
• Reports

#### Why are error budgets measured in minutes?​

• Error budgets are measured in percentages but we additionally display them as units of time to make them easier to comprehend. For example, 33% of a 0.1% error allowance over 28 days remaining can be more difficult to understand than We can sustain another 15 minutes of complete downtime this month.

#### Why are burn rates measured in 1x, 2x, 3x, and such?​

• Nobl9 measures burn rates in a standard way:
• 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.

#### My SLO shows a negative Error Budget Burn Rate. Is that normal?​

• If your SLO shows a negative error budget, check if your query is correct or contact support@nobl9.com.

#### My error budget is more than 100%. Is that possible?​

• If your error budget is above 100%, check if your query is correct or contact support@nobl9.com.

#### How can I remove an Alert Policy from an SLO?​

• Use alert_policies = [] command to remove an Alert Policy from the SLO.

#### How does Nobl9 query for data?​

• Nobl9 queries for data every 1-2 minutes in 20-15 second intervals. The time depens on the data source in question. For the Source-specific querying information, check the Sources section - you can find them in the Querying (data source name) Server section in each Source's subpage.

#### How fast is the error budget burning for averageBurnRate? Is that an instantaneous measurement, or over some period of time?​

• AverageBurnRate uses an average over the previous 5 minutes of instantaneous calculations. However, it can pick up spikes, for example, if you set the condition to be true for 10 minutes, it is rolling 5 min. averages over that 10 min. period.