From 9c5badeca8c14c3e7572376101b47010e0bd420c Mon Sep 17 00:00:00 2001 From: Catherine Luse Date: Thu, 18 Jul 2019 17:14:18 -0700 Subject: [PATCH 1/7] Explain out-of-the-box alerts --- .../v2.x/en/cluster-admin/tools/_index.md | 2 + .../en/cluster-admin/tools/alerts/_index.md | 2 + .../tools/alerts/default-alerts/_index.md | 74 +++++++++++++++++++ 3 files changed, 78 insertions(+) create mode 100644 content/rancher/v2.x/en/cluster-admin/tools/alerts/default-alerts/_index.md diff --git a/content/rancher/v2.x/en/cluster-admin/tools/_index.md b/content/rancher/v2.x/en/cluster-admin/tools/_index.md index 7cec8deaebd..24546694143 100644 --- a/content/rancher/v2.x/en/cluster-admin/tools/_index.md +++ b/content/rancher/v2.x/en/cluster-admin/tools/_index.md @@ -23,6 +23,8 @@ Notifiers and alerts are two features that work together to inform you of events Notifiers and alerts are built on top of the [Prometheus Alertmanager](https://prometheus.io/docs/alerting/alertmanager/). Leveraging these tools, Rancher can notify [cluster owners]({{< baseurl >}}/rancher/v2.x/en/admin-settings/rbac/cluster-project-roles/#cluster-roles) and [project owners]({{< baseurl >}}/rancher/v2.x/en/admin-settings/rbac/cluster-project-roles/#project-roles) of events they need to address. +When you create a cluster and enable monitoring for the cluster, some alerts are added by default. For details, refer to the [documentation on default alerts.]({{< baseurl >}}/rancher/v2.x/en/cluster-admin/tools/alerts/default-alerts) + ### Notifiers Before you can receive alerts, you must configure one or more notifier in Rancher. diff --git a/content/rancher/v2.x/en/cluster-admin/tools/alerts/_index.md b/content/rancher/v2.x/en/cluster-admin/tools/alerts/_index.md index 6f2805a315f..248fc0f8714 100644 --- a/content/rancher/v2.x/en/cluster-admin/tools/alerts/_index.md +++ b/content/rancher/v2.x/en/cluster-admin/tools/alerts/_index.md @@ -7,6 +7,8 @@ To keep your clusters and applications healthy and driving your organizational p Alerts are sets of rules, chosen by you, to monitor for specific events. +When you create a cluster and enable monitoring for the cluster, some alerts are added by default. For details, refer to the [documentation on default alerts.]({{< baseurl >}}/rancher/v2.x/en/cluster-admin/tools/alerts/default-alerts) + ## Alerts Scope The scope for alerts can be set at either the cluster level or [project level]({{< baseurl >}}/rancher/v2.x/en/project-admin/tools/alerts/). diff --git a/content/rancher/v2.x/en/cluster-admin/tools/alerts/default-alerts/_index.md b/content/rancher/v2.x/en/cluster-admin/tools/alerts/default-alerts/_index.md new file mode 100644 index 00000000000..12a393236cf --- /dev/null +++ b/content/rancher/v2.x/en/cluster-admin/tools/alerts/default-alerts/_index.md @@ -0,0 +1,74 @@ +--- +title: Default Alerts +weight: 1 +--- + +# Overview of Default Alerts for Cluster Monitoring + +When you enable monitoring for a cluster, Rancher provides several alerts by default. These alerts notify you about signs that the cluster could be unhealthy. + +Several of the alerts use Prometheus expressions as the metric that triggers the alert. For more information on how expressions work, you can refer to the Rancher [documentation about Prometheus expressions]({{< baseurl >}} +/rancher/v2.x/en/cluster-admin/tools/monitoring/expression/) or the Prometheus [documentation about querying metrics](https://prometheus.io/docs/prometheus/latest/querying/basics/). + +>**Prerequisite:** Before you can receive cluster alerts, you must [add a notifier]({{< baseurl >}}/rancher/v2.x/en/cluster-admin/tools/notifiers/#adding-notifiers). + +# Alerts for etcd +Etcd is the key-value store that contains the state of the Kubernetes cluster. If you provide monitoring on your cluster, Rancher provides default alerts if the monitoring detects a potential problem with etcd. + +A leader is the node that handles all client requests that need cluster consensus. For more information, you can refer to this [explanation of how etcd works.](https://rancher.com/blog/2019/2019-01-29-what-is-etcd/#how-does-etcd-work) + +### Alert: A high number of leader changes within the etcd cluster are happening +A warning alert is triggered when the leader changes more than three times in one hour. + +The leader of the cluster can change in response to certain events. It is normal for the leader to change, but too many changes can indicate a problem with the network or a high CPU load. With longer latencies, the default etcd configuration may cause frequent heartbeat timeouts, which trigger a new leader election. + +### Alert: Database usage close to the quota 500M +A warning alert is triggered when the size of etcd exceeds 524,288,000 bytes. + +### Alert: Etcd is unavailable +A critical alert is triggered when etcd becomes unavailable. + +### Alert: Etcd member has no leader +A critical alert is triggered when etcd does not have a leader for at least three minutes. + +# Alerts for Kube Components +Rancher provides alerts when core Kubernetes system components become unhealthy. + +### Alert: Controller Manager is unavailable +A critical warning is triggered when the cluster’s controller-manager becomes unavailable. + +Controllers update Kubernetes resources based on changes in etcd. The [controller manager](https://kubernetes.io/docs/reference/command-line-tools-reference/kube-controller-manager/) monitors the cluster desired state through the Kubernetes API server and makes the necessary changes to the current state to reach the desired state. + +### Alert: Scheduler is unavailable +A critical warning is triggered when the cluster’s scheduler becomes unavailable. + +The [scheduler](https://kubernetes.io/docs/reference/command-line-tools-reference/kube-scheduler/) service is a core component of Kubernetes. It is responsible for scheduling cluster workloads to nodes, based on various configurations, metrics, resource requirements and workload-specific requirements. + +# Alerts for Events +Events can trigger alerts. + +### Alert: Get warning deployment event +A warning alert is triggered when a deployment event happens. + +# Alerts for Node +Alerts can be triggered based on node metrics. + +### Alert: High CPU load +A warning alert is triggered if the node uses more than 100 percent of the node’s available CPU seconds for at least three minutes. + +### Alert: High node memory utilization +A warning alert is triggered if the node uses more than 80 percent of its available memory for at least three minutes. + +### Alert: Node disk is running full within 24 hours +A critical alert is triggered if the disk space on the node is expected to run out in the next 24 hours based on the disk growth over the last 6 hours. + + +# Project-level Alerts +When you enable monitoring for the project, some project-level alerts are provided. + +### Alert: Less than half workload available +A critical alert is triggered if less than half of a workload is available, based on workloads where the key is `app` and the value is `workload.` + +### Alert: Memory usage close to the quota +A warning alert is triggered if the project's memory usage exceeds the memory resource limits for the project. + From 950c8ce9c561ed0f8e88850763da879b7cb5e6ca Mon Sep 17 00:00:00 2001 From: Catherine Luse Date: Thu, 8 Aug 2019 13:33:07 -0700 Subject: [PATCH 2/7] Change default alert paragraphs to tables --- .../tools/alerts/default-alerts/_index.md | 58 ++++++++----------- 1 file changed, 25 insertions(+), 33 deletions(-) diff --git a/content/rancher/v2.x/en/cluster-admin/tools/alerts/default-alerts/_index.md b/content/rancher/v2.x/en/cluster-admin/tools/alerts/default-alerts/_index.md index 12a393236cf..9c5c327c9a4 100644 --- a/content/rancher/v2.x/en/cluster-admin/tools/alerts/default-alerts/_index.md +++ b/content/rancher/v2.x/en/cluster-admin/tools/alerts/default-alerts/_index.md @@ -17,58 +17,50 @@ Etcd is the key-value store that contains the state of the Kubernetes cluster. I A leader is the node that handles all client requests that need cluster consensus. For more information, you can refer to this [explanation of how etcd works.](https://rancher.com/blog/2019/2019-01-29-what-is-etcd/#how-does-etcd-work) -### Alert: A high number of leader changes within the etcd cluster are happening -A warning alert is triggered when the leader changes more than three times in one hour. - The leader of the cluster can change in response to certain events. It is normal for the leader to change, but too many changes can indicate a problem with the network or a high CPU load. With longer latencies, the default etcd configuration may cause frequent heartbeat timeouts, which trigger a new leader election. -### Alert: Database usage close to the quota 500M -A warning alert is triggered when the size of etcd exceeds 524,288,000 bytes. +| Alert | Explanation | +|-------|-------------| +| A high number of leader changes within the etcd cluster are happening | A warning alert is triggered when the leader changes more than three times in one hour. | +| Database usage close to the quota 500M | A warning alert is triggered when the size of etcd exceeds 524.288M.| +| Etcd is unavailable | A critical alert is triggered when etcd becomes unavailable. | +| Etcd member has no leader | A critical alert is triggered when etcd does not have a leader for at least three minutes. | -### Alert: Etcd is unavailable -A critical alert is triggered when etcd becomes unavailable. - -### Alert: Etcd member has no leader -A critical alert is triggered when etcd does not have a leader for at least three minutes. # Alerts for Kube Components Rancher provides alerts when core Kubernetes system components become unhealthy. -### Alert: Controller Manager is unavailable -A critical warning is triggered when the cluster’s controller-manager becomes unavailable. - Controllers update Kubernetes resources based on changes in etcd. The [controller manager](https://kubernetes.io/docs/reference/command-line-tools-reference/kube-controller-manager/) monitors the cluster desired state through the Kubernetes API server and makes the necessary changes to the current state to reach the desired state. -### Alert: Scheduler is unavailable -A critical warning is triggered when the cluster’s scheduler becomes unavailable. - The [scheduler](https://kubernetes.io/docs/reference/command-line-tools-reference/kube-scheduler/) service is a core component of Kubernetes. It is responsible for scheduling cluster workloads to nodes, based on various configurations, metrics, resource requirements and workload-specific requirements. +| Alert | Explanation | +|-------|-------------| +| Controller Manager is unavailable | A critical warning is triggered when the cluster’s controller-manager becomes unavailable. | +| Scheduler is unavailable | A critical warning is triggered when the cluster’s scheduler becomes unavailable. | + + # Alerts for Events Events can trigger alerts. -### Alert: Get warning deployment event -A warning alert is triggered when a deployment event happens. +| Alert | Explanation | +|-------|-------------| +| Get warning deployment event | A warning alert is triggered by a deployment event happens. | + # Alerts for Node Alerts can be triggered based on node metrics. -### Alert: High CPU load -A warning alert is triggered if the node uses more than 100 percent of the node’s available CPU seconds for at least three minutes. - -### Alert: High node memory utilization -A warning alert is triggered if the node uses more than 80 percent of its available memory for at least three minutes. - -### Alert: Node disk is running full within 24 hours -A critical alert is triggered if the disk space on the node is expected to run out in the next 24 hours based on the disk growth over the last 6 hours. - +| Alert | Explanation | +|-------|-------------| +| High CPU load | A warning alert is triggered if the node uses more than 100 percent of the node’s available CPU seconds for at least three minutes. | +| High node memory utilization | A warning alert is triggered if the node uses more than 80 percent of its available memory for at least three minutes. | +| Node disk is running full within 24 hours | A critical alert is triggered if the disk space on the node is expected to run out in the next 24 hours based on the disk growth over the last 6 hours. | # Project-level Alerts When you enable monitoring for the project, some project-level alerts are provided. -### Alert: Less than half workload available -A critical alert is triggered if less than half of a workload is available, based on workloads where the key is `app` and the value is `workload.` - -### Alert: Memory usage close to the quota -A warning alert is triggered if the project's memory usage exceeds the memory resource limits for the project. - +| Alert | Explanation | +|-------|-------------| +| Less than half workload available | A critical alert is triggered if less than half of a workload is available, based on workloads where the key is `app` and the value is `workload.` | +| Memory usage close to the quota | A warning alert is triggered if the project's memory usage exceeds the memory resource limits for the project. | \ No newline at end of file From b4305b335a61b84f33193a0442a24c65a5323a28 Mon Sep 17 00:00:00 2001 From: Catherine Luse Date: Thu, 18 Jul 2019 17:14:18 -0700 Subject: [PATCH 3/7] Explain out-of-the-box alerts --- .../v2.x/en/cluster-admin/tools/alerts/default-alerts/_index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/rancher/v2.x/en/cluster-admin/tools/alerts/default-alerts/_index.md b/content/rancher/v2.x/en/cluster-admin/tools/alerts/default-alerts/_index.md index 9c5c327c9a4..9ee8043da33 100644 --- a/content/rancher/v2.x/en/cluster-admin/tools/alerts/default-alerts/_index.md +++ b/content/rancher/v2.x/en/cluster-admin/tools/alerts/default-alerts/_index.md @@ -63,4 +63,4 @@ When you enable monitoring for the project, some project-level alerts are provid | Alert | Explanation | |-------|-------------| | Less than half workload available | A critical alert is triggered if less than half of a workload is available, based on workloads where the key is `app` and the value is `workload.` | -| Memory usage close to the quota | A warning alert is triggered if the project's memory usage exceeds the memory resource limits for the project. | \ No newline at end of file +| Memory usage close to the quota | A warning alert is triggered if the project's memory usage exceeds the memory resource limits for the project. | From b91cc50d7cdc07e6ded2e29002750632944b9b12 Mon Sep 17 00:00:00 2001 From: Catherine Luse Date: Fri, 9 Aug 2019 17:22:53 -0700 Subject: [PATCH 4/7] Add info to out-of-the-box alerts page --- .../cluster-admin/tools/alerts/default-alerts/_index.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/content/rancher/v2.x/en/cluster-admin/tools/alerts/default-alerts/_index.md b/content/rancher/v2.x/en/cluster-admin/tools/alerts/default-alerts/_index.md index 9ee8043da33..ce7a4e28083 100644 --- a/content/rancher/v2.x/en/cluster-admin/tools/alerts/default-alerts/_index.md +++ b/content/rancher/v2.x/en/cluster-admin/tools/alerts/default-alerts/_index.md @@ -41,11 +41,11 @@ The [scheduler](https://kubernetes.io/docs/reference/command-line-tools-referenc # Alerts for Events -Events can trigger alerts. +Kubernetes events are objects that provide insight into what is happening inside a cluster, such as what decisions were made by the scheduler or why some pods were evicted from the node. In the Rancher UI, from the project view, you can see events for each workload. | Alert | Explanation | |-------|-------------| -| Get warning deployment event | A warning alert is triggered by a deployment event happens. | +| Get warning deployment event | A warning alert is triggered by a warning event happens on a deployment. | # Alerts for Node @@ -62,5 +62,5 @@ When you enable monitoring for the project, some project-level alerts are provid | Alert | Explanation | |-------|-------------| -| Less than half workload available | A critical alert is triggered if less than half of a workload is available, based on workloads where the key is `app` and the value is `workload.` | -| Memory usage close to the quota | A warning alert is triggered if the project's memory usage exceeds the memory resource limits for the project. | +| Less than half workload available | A critical alert is triggered if less than half of a workload is available, based on workloads where the key is `app` and the value is `workload`. | +| Memory usage close to the quota | A warning alert is triggered if the project's memory usage exceeds the memory resource quota that is set for the workload. You can see the memory limit in the Rancher UI if you go to the workload under the **Security & Host Config** tab. | \ No newline at end of file From b351654419ae1d062721e1c7cbb44b5aa7cecc70 Mon Sep 17 00:00:00 2001 From: Catherine Luse Date: Thu, 15 Aug 2019 11:37:35 -0700 Subject: [PATCH 5/7] Edit docs for default cluster alerts --- .../v2.x/en/cluster-admin/tools/alerts/_index.md | 4 +++- .../tools/alerts/default-alerts/_index.md | 16 ++++++---------- 2 files changed, 9 insertions(+), 11 deletions(-) diff --git a/content/rancher/v2.x/en/cluster-admin/tools/alerts/_index.md b/content/rancher/v2.x/en/cluster-admin/tools/alerts/_index.md index 248fc0f8714..9ac774135f4 100644 --- a/content/rancher/v2.x/en/cluster-admin/tools/alerts/_index.md +++ b/content/rancher/v2.x/en/cluster-admin/tools/alerts/_index.md @@ -7,7 +7,9 @@ To keep your clusters and applications healthy and driving your organizational p Alerts are sets of rules, chosen by you, to monitor for specific events. -When you create a cluster and enable monitoring for the cluster, some alerts are added by default. For details, refer to the [documentation on default alerts.]({{< baseurl >}}/rancher/v2.x/en/cluster-admin/tools/alerts/default-alerts) +When you create a cluster, some alert rules are predefined. You can receive these alerts if you configure a [notifier]({{}}/rancher/v2.x/en/cluster-admin/tools/notifiers) for them. + +For details about what triggers the predefined alerts, refer to the [documentation on default alerts.]({{< baseurl >}}/rancher/v2.x/en/cluster-admin/tools/alerts/default-alerts) ## Alerts Scope diff --git a/content/rancher/v2.x/en/cluster-admin/tools/alerts/default-alerts/_index.md b/content/rancher/v2.x/en/cluster-admin/tools/alerts/default-alerts/_index.md index ce7a4e28083..4287b83f649 100644 --- a/content/rancher/v2.x/en/cluster-admin/tools/alerts/default-alerts/_index.md +++ b/content/rancher/v2.x/en/cluster-admin/tools/alerts/default-alerts/_index.md @@ -1,17 +1,13 @@ --- -title: Default Alerts +title: Default Alerts for Cluster Monitoring weight: 1 --- -# Overview of Default Alerts for Cluster Monitoring - -When you enable monitoring for a cluster, Rancher provides several alerts by default. These alerts notify you about signs that the cluster could be unhealthy. +When you create a cluster, some alert rules are predefined. These alerts notify you about signs that the cluster could be unhealthy. You can receive these alerts if you configure a [notifier]({{}}/rancher/v2.x/en/cluster-admin/tools/notifiers) for them. Several of the alerts use Prometheus expressions as the metric that triggers the alert. For more information on how expressions work, you can refer to the Rancher [documentation about Prometheus expressions]({{< baseurl >}} /rancher/v2.x/en/cluster-admin/tools/monitoring/expression/) or the Prometheus [documentation about querying metrics](https://prometheus.io/docs/prometheus/latest/querying/basics/). ->**Prerequisite:** Before you can receive cluster alerts, you must [add a notifier]({{< baseurl >}}/rancher/v2.x/en/cluster-admin/tools/notifiers/#adding-notifiers). - # Alerts for etcd Etcd is the key-value store that contains the state of the Kubernetes cluster. If you provide monitoring on your cluster, Rancher provides default alerts if the monitoring detects a potential problem with etcd. @@ -22,9 +18,9 @@ The leader of the cluster can change in response to certain events. It is normal | Alert | Explanation | |-------|-------------| | A high number of leader changes within the etcd cluster are happening | A warning alert is triggered when the leader changes more than three times in one hour. | -| Database usage close to the quota 500M | A warning alert is triggered when the size of etcd exceeds 524.288M.| +| Database usage close to the quota 500M | A warning alert is triggered when the size of etcd exceeds 500M.| | Etcd is unavailable | A critical alert is triggered when etcd becomes unavailable. | -| Etcd member has no leader | A critical alert is triggered when etcd does not have a leader for at least three minutes. | +| Etcd member has no leader | A critical alert is triggered when the etcd cluster does not have a leader for at least three minutes. | # Alerts for Kube Components @@ -48,7 +44,7 @@ Kubernetes events are objects that provide insight into what is happening inside | Get warning deployment event | A warning alert is triggered by a warning event happens on a deployment. | -# Alerts for Node +# Alerts for Nodes Alerts can be triggered based on node metrics. | Alert | Explanation | @@ -63,4 +59,4 @@ When you enable monitoring for the project, some project-level alerts are provid | Alert | Explanation | |-------|-------------| | Less than half workload available | A critical alert is triggered if less than half of a workload is available, based on workloads where the key is `app` and the value is `workload`. | -| Memory usage close to the quota | A warning alert is triggered if the project's memory usage exceeds the memory resource quota that is set for the workload. You can see the memory limit in the Rancher UI if you go to the workload under the **Security & Host Config** tab. | \ No newline at end of file +| Memory usage close to the quota | A warning alert is triggered if the workload's memory usage exceeds the memory resource quota that is set for the workload. You can see the memory limit in the Rancher UI if you go to the workload under the **Security & Host Config** tab. | \ No newline at end of file From eab77737fa9415a9c61b9cbbdf1516a8a8ce55a9 Mon Sep 17 00:00:00 2001 From: Catherine Luse Date: Thu, 15 Aug 2019 21:39:54 -0700 Subject: [PATCH 6/7] Update _index.md --- content/rancher/v2.x/en/cluster-admin/tools/_index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/rancher/v2.x/en/cluster-admin/tools/_index.md b/content/rancher/v2.x/en/cluster-admin/tools/_index.md index 24546694143..a03c09c0c1a 100644 --- a/content/rancher/v2.x/en/cluster-admin/tools/_index.md +++ b/content/rancher/v2.x/en/cluster-admin/tools/_index.md @@ -23,7 +23,7 @@ Notifiers and alerts are two features that work together to inform you of events Notifiers and alerts are built on top of the [Prometheus Alertmanager](https://prometheus.io/docs/alerting/alertmanager/). Leveraging these tools, Rancher can notify [cluster owners]({{< baseurl >}}/rancher/v2.x/en/admin-settings/rbac/cluster-project-roles/#cluster-roles) and [project owners]({{< baseurl >}}/rancher/v2.x/en/admin-settings/rbac/cluster-project-roles/#project-roles) of events they need to address. -When you create a cluster and enable monitoring for the cluster, some alerts are added by default. For details, refer to the [documentation on default alerts.]({{< baseurl >}}/rancher/v2.x/en/cluster-admin/tools/alerts/default-alerts) +When you create a cluster, some alert rules are predefined. For details, refer to the [documentation on default alerts.]({{< baseurl >}}/rancher/v2.x/en/cluster-admin/tools/alerts/default-alerts) ### Notifiers From af483bddbea5e3cdddf11acdf7d6c547e170ff40 Mon Sep 17 00:00:00 2001 From: Catherine Luse Date: Mon, 19 Aug 2019 15:48:56 -0700 Subject: [PATCH 7/7] Minor edits to default alert docs --- .../cluster-admin/tools/alerts/default-alerts/_index.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/content/rancher/v2.x/en/cluster-admin/tools/alerts/default-alerts/_index.md b/content/rancher/v2.x/en/cluster-admin/tools/alerts/default-alerts/_index.md index 4287b83f649..63ad50061d8 100644 --- a/content/rancher/v2.x/en/cluster-admin/tools/alerts/default-alerts/_index.md +++ b/content/rancher/v2.x/en/cluster-admin/tools/alerts/default-alerts/_index.md @@ -9,7 +9,7 @@ Several of the alerts use Prometheus expressions as the metric that triggers the /rancher/v2.x/en/cluster-admin/tools/monitoring/expression/) or the Prometheus [documentation about querying metrics](https://prometheus.io/docs/prometheus/latest/querying/basics/). # Alerts for etcd -Etcd is the key-value store that contains the state of the Kubernetes cluster. If you provide monitoring on your cluster, Rancher provides default alerts if the monitoring detects a potential problem with etcd. +Etcd is the key-value store that contains the state of the Kubernetes cluster. Rancher provides default alerts if the built-in monitoring detects a potential problem with etcd. You don't have to enable monitoring to receive these alerts. A leader is the node that handles all client requests that need cluster consensus. For more information, you can refer to this [explanation of how etcd works.](https://rancher.com/blog/2019/2019-01-29-what-is-etcd/#how-does-etcd-work) @@ -23,7 +23,7 @@ The leader of the cluster can change in response to certain events. It is normal | Etcd member has no leader | A critical alert is triggered when the etcd cluster does not have a leader for at least three minutes. | -# Alerts for Kube Components +# Alerts for Kubernetes Components Rancher provides alerts when core Kubernetes system components become unhealthy. Controllers update Kubernetes resources based on changes in etcd. The [controller manager](https://kubernetes.io/docs/reference/command-line-tools-reference/kube-controller-manager/) monitors the cluster desired state through the Kubernetes API server and makes the necessary changes to the current state to reach the desired state. @@ -41,11 +41,11 @@ Kubernetes events are objects that provide insight into what is happening inside | Alert | Explanation | |-------|-------------| -| Get warning deployment event | A warning alert is triggered by a warning event happens on a deployment. | +| Get warning deployment event | A warning alert is triggered when a warning event happens on a deployment. | # Alerts for Nodes -Alerts can be triggered based on node metrics. +Alerts can be triggered based on node metrics. Each computing resource in a Kubernetes cluster is called a node. [Nodes]({{}}/rancher/v2.x/en/cluster-admin/#kubernetes-cluster-node-components) can be either bare-metal servers or virtual machines. | Alert | Explanation | |-------|-------------|