Page tree
Skip to end of metadata
Go to start of metadata

  1. On the SLO Management console, click the SLO Administration tab.
  2. Click the relevant option:
    • For a new SLO, click Add.
    • To edit an existing SLO, click Edit.
  3. On the first screen (Step 1) of the SLO wizard, specify or modify the SLO attributes summarized in the following table, and then click Next.

    Note

    Only the fields indicated by a red asterisk are mandatory. For all other SLO attributes, you can accept the default settings.

    Attributes for defining an SLO

    SLO attributeDescription
    NameA unique name for the SLO.
    OwnerName of the user who owns the SLO.
    Contact InformationPhone number or email address of the SLO owner.
    SLO Contents

     

    Type of objects that compose the SLO, SLOs, or instances

    • SLOs based on instances form base-level SLOs
    • SLOs based on SLOs provide a consolidated view of related SLOs. The grouping can include SLOs based on instances and other nested SLOs.

    If you choose SLOs, you can create an SLO only for classification by selecting the Use this SLO for grouping only, and not to calculate Aggregate Compliance values option.

     

    Copy from GroupsCheck this option and select groups to copy from the existing groups. This option is static and acts as a filter.
    SLO TypeThe type of SLO based on the groups to which it is associated. 
    Basic SLO types are Availability, Response Time, and System Performance. You can add other types or edit the attributes of the SLO types at this point. See Managing SLO types during SLO configuration.
    Create corresponding Response Time SLOSelect this check box if you chose Availability as the SLO type and want a corresponding Response Time SLO created, or if you chose Response Time as the SLO type and want a corresponding Availability SLO created.
    ScheduleSelect the schedule to apply to SLO monitoring. 
    If required, you can select multiple schedules. This allows you to set threshold values for different time periods. For example, Response time threshold values may not be the same during business and non-business hours. 
    Basic schedules are 24X7 and Business Hours. You can add other schedules or edit the attributes of the schedules at this point. See Managing schedules during SLO configuration.
    SLO Compliance - ObjectivePercentage of compliance or non-compliance (as indicated and based on the SLO type) that the SLO must obtain.
    SLO Compliance - Range SetYou can add other range sets or edit the settings of the user-defined ranges at this point. See Managing range sets during SLO configuration.

     

  4. On the second screen (Step 2) of the SLO wizard, select one or more Group Filter and at least one Monitor Type to associate with the SLO, and then click Next.
  5. Select the Monitor Instances to add to the SLO, and then click Next.
  6. On the third screen (Step 3) of the SLO wizard, you can modify any of the SLO values summarized in the following table.
    • To modify a specific SLO, enter values directly in the displayed table.
    • To modify multiple SLOs, enter values in the fields below the table as described in the following table and then click Apply.

      Tip

      For guidance on setting values based on compliance values recommended for the selected monitor instances, click SLO Guidance. For more information, see Requesting guidance for setting SLO thresholds.

      Configurable SLO values

      Setting

      Description

      Service Level Objective: Condition

      Condition using which SLOs are compared with actual measurements, either Greater than or equal or Less than or equal.

      Service Level Objective: Value

      SLO value (a percentage) for the instance or attribute.

      Minimum Duration

      Time period for validating the SLO violation. Only after the SLO value has continued to stay in the violation range for a period greater than the minimum duration it is reported as a violation.

      Weight

      Weight associated with the SLO attribute, a whole number greater than zero.
      Associated Weights define the relative importance of an attribute within the SLO (for computation requirements). For example, if Attributes A, B, and C have associated weights of 5, 10, and 15 (respectively), then Attribute C is thrice as important as A, and B is twice as important as A.
      To ignore SLO violations during computation, specify a weight of zero.

      Financial Impact

      Amount of financial loss (per hour) caused if the SLO condition is not met.

  7. If you want intelligent event thresholds created for all the listed SLO, select the Set corresponding Instance Intelligent Event Threshold option, and then specify the severity and duration for the event.
  8. If you are defining Transaction Monitors, such as a Web Transaction, you can now add (and subsequently delete) sub-transactions on the displayed list.
  9. To add a sub-transaction, click Add Sub-Transactions, select sub-transactions from the displayed list and click Apply.
  10. To delete sub-transactions, select the relevant sub-transactions and click Delete Sub-Transactions, and then click OK in the confirmation message.
  11. Click Finish.
    The new SLO is created and displayed in the SLO list on the SLO Administration screen.