Skip to content

Contact sales

By filling out this form and clicking submit, you acknowledge our privacy policy.
  • Labs icon Lab
  • A Cloud Guru
Google Cloud Platform icon

Creating Alerting Rules

After deploying a Prometheus environment to our Kubernetes cluster, the team has decided to test its monitoring capabilities by configuring alerting of our Redis deployment. We have been tasked with writing two alerting rules. The first rule will fire an alert if any of the Redis pods are down for 10 minutes. The second alert will fire if there are no pods available for 1 minute.

Google Cloud Platform icon

Path Info

Clock icon Intermediate
Clock icon 1h 0m
Clock icon Jan 21, 2019

Contact sales

By filling out this form and clicking submit, you acknowledge our privacy policy.

Table of Contents

  1. Challenge

    Create a ConfigMap That Will Be Used to Manage the Alerting Rules

    Edit prometheus-rules-config-map.yml and add the Redis alerting rules. It should look like this when we're done:

    apiVersion: v1
    kind: ConfigMap
      creationTimestamp: null
      name: prometheus-rules-conf
      namespace: monitoring
      redis_rules.yml: |
        - name: redis_rules
          - record: redis:command_call_duration_seconds_count:rate2m
            expr: sum(irate(redis_command_call_duration_seconds_count[2m])) by (cmd, environment)
          - record: redis:total_requests:rate2m
            expr: rate(redis_commands_processed_total[2m])
      redis_alerts.yml: |
        - name: redis_alerts
          - alert: RedisServerDown
            expr: redis_up{app="media-redis"} == 0
            for: 10m
              severity: critical
              summary: Redis Server {{ $labels.instance }} is down!
          - alert: RedisServerGone
            expr:  absent(redis_up{app="media-redis"})
            for: 1m
              severity: critical
              summary: No Redis servers are reporting!
  2. Challenge

    Apply the Changes Made to `prometheus-rules-config-map.yml`

    Now, apply the changes that were made to prometheus-rules-config-map.yml:

    kubectl apply -f prometheus-rules-config-map.yml
  3. Challenge

    Delete the Prometheus Pod

    1. List the pods to find the name of the Prometheus pod:
    kubectl get pods -n monitoring
    1. Delete the Prometheus pod:
    kubectl delete pods <POD_NAME> -n monitoring
    1. In a new browser tab, navigate to the Expression browser:
    1. Click on the Alerts link to verify that the two Redis alerts are showing as green.

The Cloud Content team comprises subject matter experts hyper focused on services offered by the leading cloud vendors (AWS, GCP, and Azure), as well as cloud-related technologies such as Linux and DevOps. The team is thrilled to share their knowledge to help you build modern tech solutions from the ground up, secure and optimize your environments, and so much more!

What's a lab?

Hands-on Labs are real environments created by industry experts to help you learn. These environments help you gain knowledge and experience, practice without compromising your system, test without risk, destroy without fear, and let you learn from your mistakes. Hands-on Labs: practice your skills before delivering in the real world.

Provided environment for hands-on practice

We will provide the credentials and environment necessary for you to practice right within your browser.

Guided walkthrough

Follow along with the author’s guided walkthrough and build something new in your provided environment!

Did you know?

On average, you retain 75% more of your learning if you get time for practice.

Start learning by doing today

View Plans