anchor.diff:      - name: 'rabbitmq-queue-warning'
         description: 'The number of outstanding messages is too high'
         severity: 'warning'
  +      # If the local RabbitMQ instance is down, it will be caught by the
  +      # rabbitmq-check alarm
  +      no_data_policy: 'okay'
         enabled: 'true'
         trigger:
           logical_operator: 'or'
  
positive.code:             periods: 0
              function: avg
      - name: 'rabbitmq-pacemaker-down'
        description: 'The RabbitMQ cluster is down because less than half of the nodes are up'
        severity: 'down'
        no_data_policy: 'skip' # the metric is only collected from the DC node
        enabled: 'true'
        trigger:
  
negative.code:             function: last
      - name: 'rabbitmq-check'
        description: "RabbitMQ cannot be checked"
        # This alarm's severity is warning because the effective status of the
        # RabbitMQ cluster is computed by rabbitmq-pacemaker-* alarms.
        # This alarm is still useful because it will report the node(s) on which
        # RabbitMQ isn't running.
        severity: 'warning'
        enabled: 'true'
        trigger:
          rules:
  