This alert triggers when the average memory utilization of containers in an Amazon EKS cluster exceeds 80%. High memory utilization can lead to container performance issues or even crashes if it reaches critical levels. Customization Guidance: Threshold: The alert is set to trigger at 80% memory utilization. Adjust this threshold based on your environment's tolerance for high memory usage. Cluster Specificity: Customize the alert for different clusters based on their criticality and expected memory consumption. Notification Frequency: Ensure timely notifications to prevent container failures due to memory exhaustion. Action: Monitor container performance, scale resources if necessary, and optimize container memory usage.

This alert triggers when the average CPU utilization of containers in an Amazon EKS cluster exceeds 80%. High CPU utilization can cause containers to slow down or become unresponsive. Customization Guidance: Threshold: The alert is set at 80% CPU utilization. Adjust this threshold based on your environment's needs. Cluster Specificity: Tailor the alert to specific clusters to manage CPU-intensive workloads effectively. Notification Frequency: Adjust the frequency to balance responsiveness with alert fatigue. Action: Review and optimize container CPU usage, and consider scaling the cluster if necessary.

This alert triggers when the maximum memory utilization of pods in an Amazon EKS cluster exceeds 80%. Excessive memory usage at the pod level can lead to out-of-memory (OOM) errors and disrupt application availability. Customization Guidance: Threshold: The default threshold is set at 80% memory utilization. Adjust this based on the application's memory requirements. Pod Specificity: Focus on critical pods where memory overutilization could severely impact application performance. Notification Frequency: Set notifications to quickly detect and mitigate memory issues.

This alert triggers when the average CPU utilization of pods in an Amazon EKS cluster exceeds 80%. High CPU usage at the pod level can cause performance degradation and slow response times. Customization Guidance: Threshold: The alert is triggered at 80% CPU utilization. Adjust the threshold based on your pod's expected CPU consumption. Pod Specificity: Customize the alert for critical pods to ensure high performance and availability. Notification Frequency: Ensure timely alerts to prevent CPU-related performance issues. Action: Monitor and optimize CPU usage within pods, and scale resources if necessary.

This alert triggers when there is a failed pod status detected in an Amazon EKS cluster. Failed pods can indicate issues with the underlying infrastructure or application code. Customization Guidance: Threshold: The alert is triggered by any instance of a failed pod status. Adjust alert sensitivity based on the criticality of your workloads. Cluster Specificity: Focus on clusters where pod failures would have the most significant impact. Notification Frequency: Set alerts to notify immediately upon detection of failed pods. Action: Investigate the cause of the pod failure, check logs, and resolve underlying issues promptly.

This alert triggers when the average filesystem utilization of nodes in an Amazon EKS cluster exceeds 80%. High filesystem utilization can lead to disk exhaustion, causing pods to fail or degrade in performance. Customization Guidance: Threshold: The default threshold is 80% filesystem utilization. Adjust this threshold based on your nodes' storage capacity. Node Specificity: Customize alerts for nodes with critical workloads or limited storage capacity. Notification Frequency: Optimize notifications to prevent disk space-related issues. Action: Monitor and manage disk usage, clean up unnecessary files, or expand storage as needed.

This alert triggers when the CPU utilization of nodes in an Amazon EKS cluster exceeds 80%. High CPU usage at the node level can impact the overall performance of the cluster. Customization Guidance: Threshold: Set at 80% CPU utilization, this threshold can be adjusted based on node capacity and workload demands. Node Specificity: Focus on critical nodes where high CPU usage could affect the entire cluster. Notification Frequency: Ensure that alerts are frequent enough to catch spikes in CPU utilization early. Action: Monitor node performance, optimize workloads, and scale nodes if necessary.

This alert triggers when a worker node in an Amazon EKS cluster fails. Worker node failures can disrupt the availability and performance of applications running in the cluster. Customization Guidance: Threshold: The alert triggers on any instance of a failed worker node. Adjust sensitivity based on the cluster's redundancy and failover capabilities. Cluster Specificity: Focus on clusters where worker node availability is critical to business operations. Notification Frequency: Set alerts to notify immediately upon detection of a failed worker node. Action: Investigate the cause of the node failure, initiate failover procedures, and ensure the cluster's resilience.