Define a custom condition to trigger actions

  • Versão de lançamento: Australia
  • Atualizado 12 de mar. de 2026
  • 1 min. de leitura

    • The base-system SR Ops application supports the actions of sending notifications when an alert is received and when an incident is created. You can define both custom actions and custom conditions that trigger an action. Control when a flow takes a specific decision outcome or waits for a specific resume event.

    Antes de Iniciar

    Role required: sro_admin or sro_manager

    Procedimento

    1. Navigate to All > Site Reliability Operations > Service Health > Conditions.

      The Condition form opens.

    2. On the Condition form, click New.
    3. On the form, fill in the fields.
      Tabela 1. Condition form
      Field Description
      Name Name for the condition.
      Description Description of the condition that will help others to understand its purpose.
      Applies to Type of entity against which the condition must be applied.
      Type Type of condition:
      • Criteria: Set of parameter:value pair conditions to apply against the data.
      • Script: Code that applies the condition against data.
      Conditions Set of parameter:value pair conditions to apply against the data. Select parameters and values to create conditions and logical operators to join conditions.

      This option appears only if the Type value is Criteria.
      Script Code that applies the condition against data.

      This option appears only if the Type value is Script.
    4. Click Preview to apply the condition to current data.
      The system returns a link that indicates how many records match the condition. Click the link to view the results.
    5. When you finish defining the condition, click Submit.

    Exemplo

    This example condition matches only critical alerts.

    Figura 1. Example of the critical-only alerts condition
    Example "critical-only alerts" condition shows all settings.