< img height="1" width="1" style="display:none;" alt="" src="https://px.ads.linkedin.com/collect/?pid=3131724&fmt=gif" />

KubeSphere Alerting

Alerting is an important building block of observability, closely related to monitoring and logging. The alerting system in KubeSphere, coupled with the proactive failure notification system, allows users to know activities of interest based on alerting policies. When a predefined threshold of a certain metric is reached, an alert will be sent to preconfigured recipients. Therefore, you need to configure the notification method beforehand, including Email, Slack, DingTalk, WeCom and Webhook. With a highly functional alerting and notification system in place, you can quickly identify and resolve potential issues in advance before they affect your business.

Enable Alerting before Installation

Installing on Linux

When you implement multi-node installation of KubeSphere on Linux, you need to create a configuration file, which lists all KubeSphere components.

  1. In the tutorial of Installing KubeSphere on Linux, you create a default file config-sample.yaml. Modify the file by executing the following command:

    vi config-sample.yaml
    

    Note

    If you adopt All-in-One Installation, you do not need to create a config-sample.yaml file as you can create a cluster directly. Generally, the all-in-one mode is for users who are new to KubeSphere and look to get familiar with the system. If you want to enable Alerting in this mode (for example, for testing purposes), refer to the following section to see how Alerting can be enabled after installation.
  2. In this file, navigate to alerting and change false to true for enabled. Save the file after you finish.

    alerting:
      enabled: true # Change "false" to "true".
    
  3. Create a cluster using the configuration file:

    ./kk create cluster -f config-sample.yaml
    

Installing on Kubernetes

As you install KubeSphere on Kubernetes, you can enable Alerting first in the cluster-configuration.yaml file.

  1. Download the file cluster-configuration.yaml and edit it.

    vi cluster-configuration.yaml
    
  2. In this local cluster-configuration.yaml file, navigate to alerting and enable it by changing false to true for enabled. Save the file after you finish.

    alerting:
      enabled: true # Change "false" to "true".
    
  3. Execute the following commands to start installation:

    kubectl apply -f https://github.com/kubesphere/ks-installer/releases/download/v3.1.1/kubesphere-installer.yaml
       
    kubectl apply -f cluster-configuration.yaml
    

Enable Alerting after Installation

  1. Log in to the console as admin. Click Platform in the top-left corner and select Cluster Management.

  2. Click CRDs and enter clusterconfiguration in the search bar. Click the result to view its detail page.

    Info

    A Custom Resource Definition (CRD) allows users to create a new type of resources without adding another API server. They can use these resources like any other native Kubernetes objects.
  3. In Resource List, click on the right of ks-installer and select Edit YAML.

  4. In this YAML file, navigate to alerting and change false to true for enabled. After you finish, click Update in the bottom-right corner to save the configuration.

    alerting:
      enabled: true # Change "false" to "true".
    
  5. You can use the web kubectl to check the installation process by executing the following command:

    kubectl logs -n kubesphere-system $(kubectl get pod -n kubesphere-system -l app=ks-install -o jsonpath='{.items[0].metadata.name}') -f
    

    Note

    You can find the web kubectl tool by clicking in the bottom-right corner of the console.

Verify the Installation of the Component

If you can see Alerting Messages and Alerting Policies on the Cluster Management page, it means the installation is successful as the two parts won’t display until the component is installed.

alerting-section


Thanks for the feedback. If you have a specific question about how to use KubeSphere, ask it on Slack. Open an issue in the GitHub repo if you want to report a problem or suggest an improvement.