KubeSphere alert and notification system provides flexible alerting policies and rules, including the following features:
- Support multi-tenant and multi-dimentional monitoring metrics as the alerting threshold. It allows cluster admin to set alerts for node. Tenants can also set alerts for workloads under project.
- Flexible alerting policies: users can customize the alerting policy which includes multiple rules.
- Full angle alerting metrics: provide the metrics of infrastructure and applications, including CPU, memory, disk and network.
- Flexible alerting and notification rules: support the monitoring duration, period, alerting priority. Users can customize the period time of resending alerts. Now only email delivery is supported in v2.1 (More channels will be supported in v3.0).
KubeSphere alerting and notification system requires at least 0.08 Core of CPU request and 80M of memory request. Please make sure your cluster has enough resource.
Before execute installation, you can set
true to allow both two components installation according to the following configuration, then you can back to All-in-One or Multi-Node guide to continue installation.
# Following components are all optional for KubeSphere, # Which could be turned on to install it before installation or later by updating its value to true ··· notification_enabled: true alerting_enabled: true
If you already have set up KubeSphere without enabling alerting and notification system, you still can edit the ConfigMap of ks-installer using the following command.
kubectl edit cm -n kubesphere-system ks-installer
Then set notification and alerting from
notification: enabled: True alerting: enabled: True
Save it and exit, it will be installed automatically. You can inspect the logs of ks-installer Pod to verify the installation status, and wait for the successful result logs output.