2.6. Creating alerting rules

Procedure

1. Create a YAML file for alerting rules. In this example, it is called example-app-alerting-rule.yaml.

2. Fill the file with the configuration for the alerting rules:

   注意

   When you create an alerting rule, a namespace label is enforced on it if a rule with the same name exists in another namespace.

   apiVersion: monitoring.coreos.com/v1
   kind: PrometheusRule
   metadata:
     name: example-alert
     namespace: ns1
   spec:
     groups:
     - name: example
       rules:
       - alert: VersionAlert
         expr: version{job="prometheus-example-app"} == 0

   This configuration creates an alerting rule named example-alert, which fires an alert when the version metric exposed by the sample service becomes 0.

   重要

   For every namespace, you can use metrics of that namespace and cluster metrics, but not metrics of another namespace.

   For example, an alerting rule for ns1 can have metrics from ns1 and cluster metrics, such as the CPU and memory metrics. However, the rule cannot include metrics from ns2.

   Additionally, you cannot create alerting rules for the openshift-* core OpenShift namespaces. OpenShift Container Platform Monitoring by default provides a set of alerting rules for these namespaces.

3. Apply the configuration file to the cluster:

   $ oc apply -f example-app-alerting-rule.yaml

   It will take some time to create the alerting rules.