Creating SLOs

  • 2 minute(s) read
Prev Next

Follow the steps below to create and configure a new Service Level Objective:

  1. Log into the Catchpoint Portal

  2. Navigate to Analysis > SLO > Objectives

  3. Click Create to open a new Objective properties blade.
    image.png

  4. Input a Name for this Objective (e.g. "API Performance SLO")

  5. Optionally enter a Description for the Objective

  6. Optionally specify Run From dates/times. (By default this Objective will be active immediately and run indefinitely)

  7. Select a Metric for the SLO

  8. Input a Violation Threshold (If applicable. This is the number of milliseconds that the selected metric must not exceed.)

  9. Configure the Violation Condition

  10. Select whether to base the Violation Condition on the number of Nodes that experience the issue or simply on Runs across all nodes.

    1. You can specify a number of nodes/runs that must exceed the threshold to cause a violation and/or a percentage of nodes/runs. If either the number or the percentage is exceeded, this will meet the Violation Condition and begin counting against tho SLO.
    2. If you want to require consecutive test runs to meet the violating condition when evaluating the SLO, enable consecutive.
      1. If you selected Nodes above, input the number of runs per node that must fail or exceed the threshold before that Node is considered to be in violation.
    3. Choose the time range within which multiple Nodes/Runs must fail or exceed threshold the threshold in order for a violation to be registered. (5 minutes, 10 minutes, 15 minutes, 30 minutes, or 1 hour).
    4. In the Goal section, input the percentage of the time that tests must not be in Violation Condition in order for the SLO to be met.

  11. Assign the SLO to one or more tests. (You may select tests from the list or use the search field to locate desired tests.)

  12. Configure Alerts

    1. In Recipients, select the recipients for the alert notifications.
    2. In Subject, enter the subject for the alert notifications.
    3. If you have a webhook connection enter the API endpoints for the alert notifications
    4. Under Alert Configuration, enable Budget Consumption to receive notifications when the error budget is consumed faster than expected.
      1. From SLO Window, select the SLO window.
      2. Under Thresholds, enter the Warning percentage of the budget consumed.
      3. Enter the Critical percentage of the budget consumed.
    5. Enable Burn Rate to receive notifications when the SLO is consumed faster than expected over short and long timeframes.
      1. Under Default Values, enable Use Google SRE recommended values to use the recommended burn rate values. Disable this option to configure the values manually.
      2. Under Threshold, enter the Warning burn rate and specify the short and long timeframes in minutes.
      3. Enter the Critical burn rate and specify the short and long timeframes in minutes.

  13. Click Save.