Skip to content
This repository has been archived by the owner on Jan 17, 2025. It is now read-only.

Latest commit

 

History

History
63 lines (39 loc) · 2 KB

File metadata and controls

63 lines (39 loc) · 2 KB

Alert Rules Example

Warning

This guide has been revised and moved. Find the updated instructions in Integrate With Prometheus.

Overview

This example shows how to deploy and view alerting rules in Kyma.

Prerequisites

  • Kyma as the target deployment environment.
  • Deployed custom kube-prometheus-stack as described in the prometheus example.

Installation

Add a new alerting rule

  1. Create the PrometheusRule resource holding the configuration of your alerting rule.

    kubectl apply -f https://raw.githubusercontent.com/kyma-project/examples/main/prometheus/monitoring-alert-rules/deployment/alert-rule.yaml
  2. Run the port-forward command on the monitoring-prometheus service to access the Prometheus dashboard.

    kubectl -n ${K8S_NAMESPACE} port-forward $(kubectl -n ${K8S_NAMESPACE} get service -l app=kube-prometheus-stack-prometheus -oname) 9090
  3. Go to http://localhost:9090/rules and find the pod-not-running rule.

    Because the http-db-service Deployment does not exist, Alertmanager fires an alert listed at http://localhost:9090/alerts.

Stop the alert from getting fired

  1. Export your Namespace as a variable:

    export K8S_NAMESPACE="{namespace}"
  2. To stop the alert from getting fired, create the Deployment:

    kubectl apply -f https://raw.githubusercontent.com/kyma-project/examples/main/http-db-service/deployment/deployment.yaml -n $K8S_NAMESPACE

Cleanup

Run the following commands to completely remove the example and all its resources from the cluster:

  1. Remove the pod-not-running alerting rule from the cluster:

    kubectl delete cm -n kyma-system -l example=monitoring-alert-rules
  2. Remove the http-db-service example and all its resources from the cluster:

    kubectl delete all -l example=http-db-service -n $K8S_NAMESPACE