Site Reliability Metrics change approval policies

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

    • Change approval policies use approval definitions to generate approvals based on your business requirements. A change approval policy is a course of action that can be applied to a change request.

    A change approval policy uses a set of variable inputs to evaluate the decisions that are associated with it. For each matching decision, the associated approval definition is applied. An approval policy can contain multiple decisions, such that a single policy can handle every approval required for a change type. When a decision condition matches, the related approval definition is evaluated. If one or more decisions match, all the related approval definitions are evaluated.

    To view the approval policies for SRM, navigate to Change > Change Policy > Change Approval Policies. Then, on the Change Approval Policies page, select Site Reliability Ops Change Policy.

    The Change Approval Policy page shows a list of policy inputs. You can view the following policy inputs for SRM:
    • Service Level Objective (SLO) with lowest error budget remaining percent (slo_with_lowest_error_budget_remaining_percent)
    • SLO with highest burn rate (slo_with_highest_burn_rate)
    These policy inputs should be populated with the following appropriate Service Level Objective (SLO) records:
    • The SLO with lowest error budget remaining that is relevant to the change request
    • The SLO record with the highest burn rate
    Abbildung : 1. Policy inputs for SRM
    Policy inputs for SRM.
    This approval policy contains the following two decisions for SRM:
    • Budget < 25% and Burn Rate > 1
    • Budget > 25% and Burn rate < 1

    These decisions are marked as inactive to prevent any changes in the behavior of this existing approval policy.

    You can review and use these decisions in this and other approval policies as examples of how you can base decisions on the SLO inputs.
    Abbildung : 2. SRM input decisions
    SRM input decisions.

    To provide the policy inputs related to SLO to your change approval policies, actions are created in Workflow Studio.

    An input of a comma-separated list of the sys_ids of a service is specified, but typically, an input of a single sys_id is passed. The action uses this sys_id to find all the active SLOs that are related to this service. From the SLOs that are found, the action sets:
    • The output SLO with highest burn rate to the SLO with highest burn rate value.
    • The output SLO with lowest error budget remaining percent to the SLO with the lowest value for error budget remaining percent.
    This image shows an input for the SRM – Get worst performing SLOs action.
    Abbildung : 3. Input for the SRM – Get worst performing SLOs action
    Input for the action SRM – Get worst performing SLOs.
    This image shows the output for the SRM – Get worst performing SLOs action.
    Abbildung : 4. Output for the SRM – Get worst performing SLOs action
    Output for the action SRM – Get worst performing SLOs.
    An example of this action being used to provide the inputs into the Change Approval Policy can be found in the Change - SRO - Authorize flow in Workflow Studio. The Restrict query to SLOs linked to these Service Ids field shows the action that is called with the configuration item (CI) of the change request that is authorized. The flow also shows the output from the action.
    Abbildung : 5. Output from the action
    Output from the action.
    The following outputs from the Get worst performing SLOs action can be used as inputs to the Apply Change Approval Policy action:
    • SLO with lowest error budget remaining percent
    • SLO with highest burn rate
    Abbildung : 6. Inputs for the Apply Change Approval Policy action
    Inputs for the Apply Change Approval Policy action.