Create a reliability indicator

  • Freigeben Version: Australia
  • Aktualisiert 12. März 2026
  • 2 Minuten Lesedauer

    • Create a reliability indicator to get a quantitative characterization of the reliability of your services.

    Vorbereitungen

    Role required: sn_srm_manager or sn_srm_admin or sn_srm_user

    Warum und wann dieser Vorgang ausgeführt wird

    The Site Reliability Ops Workspace view will only be available if you install the Site Reliability Operations application. You can create Service Level Indicators (SLI)s and Service Level Objectives (SLO)s using the classic environment as well. To create an SLI or SLO from the classic environment, navigate to Site Reliability Metrics > Service Level Indicators or Site Reliability Metrics > Service Level Objectives.

    Hinweis:
    You can set up only one SLO for an SLI.

    Prozedur

    1. Navigate to Site Reliability Operations > Site Reliability Ops Workspace.
    2. Click the Services page icon (Services page icon.).
      Service overview page.
    3. On the Services Overview page, click the service for which you want to create reliability indicators.
    4. Click the Reliability indicators tab.
      The Reliability indicators tab.
    5. Click New.
      Create New Service level Objective page.
    6. On the form, fill in the fields.
      Tabelle : 1. Service Level Objective form
      Field Description
      Service Level Indicator (SLI)
      Service Level Indicator (SLI) Name of the indicator.
      SLI type Type of the SLI based on which the Service Level Metrics (SLM) is calculated. The available types of SLI are as follows:
      • Latency: Time taken to service a request. The actual amount of time that elapsed.
      • Availability: Percentage of time your service is available.
      • Errors: Measurement of how frequently service error occurs.
      • Saturation: Measurement of your system fraction, emphasizing the resources that are most constrained.
      Service Service for which you are creating the reliability indicator.
      Application Performance Monitoring (APM) properties
      Name Name of the property on which the metric is based.
      Hinweis:
      The value in this field must be same as the name of the SLI in your APM tool.
      Source Data source for which the SLI must be defined.
      Operator Condition to perform specific logical function.
      Threshold Upper limit after which the metrics are triggered.
      Units Unit of measurement for the metrics.
      Service Level Objective (SLO)
      Objective type The available types of objectives are as follows:
      • Duration: Desired amount of time the service spends without breaching.
        Hinweis:
        If you select Objective type as Duration, the next two fields will be Objective period and Objective (percentage).
      • Count: Number of times an SLI is allowed to breach during a specific period.
        Hinweis:
        If you select Objective type as Count, the next two fields will be Limit period and Limit (occurrences).
      Objective period or Limit period Period for which the metrics is calculated.

      For Count as Objective type, the Limit period field appears.

      The available options are:
      • Month: The duration is considered to be the current month. For example, if the current date is 26th January, the duration will be considered from 1st January till 31st January.
      • Rolling 30 days: The duration is considered to be 30 days from the current date. For example, if the current date is 26th January, the duration will be considered from 25th December.
      • Rolling 7 days: The duration is considered to be 7 days from the current date.
      Objective (percentage) or Limit (occurrences) Percentage or count of the desired SLI performance.
    7. Click Save.
      You can see the graphical representation of the cumulative breach and the remaining error budget.
      Reliability indicator details view