This alert detects prolonged query runtime breakdown in your AWS Redshift Serverless environment. The alert is activated when query runtime exceeds a specified threshold, indicating potential inefficiencies or bottlenecks in query execution. Customization Guidance: Threshold: The default threshold is set based on typical query performance expectations. Adjust this threshold according to the specific query workload and performance benchmarks of your environment. Monitoring Period: A monitoring period of 10 minutes helps filter out transient spikes and focuses on sustained query performance issues. Adjust this period based on the criticality and complexity of your query workloads. Query Specificity: Tailor alerts for specific queries or workloads that are critical to your operations, prioritizing those with high resource demands. Notification Frequency: Consider the frequency of this alert to balance responsiveness and noise. Adjust according to the criticality of the affected workloads. Action: Upon triggering this alert, immediate actions include reviewing query plans, optimizing execution strategies, and analyzing system performance to identify potential bottlenecks.

This alert detects high compute seconds usage in your AWS Redshift Serverless environment. The alert is activated when compute seconds exceed a specified threshold, indicating potential resource inefficiencies or increased workload demands. Customization Guidance: Threshold: The default threshold is set based on expected compute usage patterns. Adjust this threshold according to your service's workload requirements and capacity planning strategies. Monitoring Period: A monitoring period of 10 minutes helps filter out transient spikes and focuses on sustained compute usage. Adjust this period according to the criticality and operational dynamics of your system. Resource Allocation: Evaluate current resource allocation and ensure compute capacity aligns with workload demands to avoid potential bottlenecks. Notification Frequency: Consider the frequency of this alert to optimize the balance between responsiveness and noise. Adjust according to the criticality of the application(s) supported. Action: Upon triggering this alert, immediate actions include reviewing compute usage trends, optimizing resource allocation, and considering scaling options to address increased demands.

This alert detects high network receive throughput in your AWS Redshift environment. The alert is activated when receive throughput exceeds a specified threshold, indicating potential network congestion or increased data ingestion. Customization Guidance: Threshold: The default threshold is set based on typical network receive patterns. Adjust this threshold according to your workload's data transfer requirements and expected network performance. Monitoring Period: A monitoring period of 5 minutes helps filter out transient spikes and focuses on sustained throughput issues. Adjust this period based on the criticality of your data transfer operations. Network Specificity: Tailor alerts for specific network interfaces or data streams that are critical to your operations, prioritizing those with high data transfer demands. Notification Frequency: Consider the frequency of this alert to balance responsiveness and noise. Adjust according to the criticality of the application(s) supported. Action: Upon triggering this alert, immediate actions include reviewing network configuration, analyzing data transfer patterns, and optimizing data ingestion processes to alleviate potential congestion.

This alert detects when maintenance mode is enabled in your AWS Redshift environment. The alert is activated when a cluster enters maintenance mode, indicating scheduled maintenance or updates. Customization Guidance: Threshold: The default threshold is set to detect any instance of maintenance mode activation. No adjustments are typically necessary unless maintenance policies vary significantly. Monitoring Period: A monitoring period of 1 minute ensures immediate detection of maintenance mode activation. Adjust this period based on your operational policies and maintenance schedules. Cluster Specificity: Tailor alerts for specific clusters based on their operational roles and maintenance schedules. Notification Frequency: Consider the frequency of this alert to ensure timely notifications while minimizing unnecessary alerts during planned maintenance. Action: Upon triggering this alert, immediate actions include reviewing maintenance schedules, notifying affected stakeholders, and ensuring that any dependencies or critical processes are accounted for during maintenance.

This alert detects high network transmit throughput in your AWS Redshift environment. The alert is activated when transmit throughput exceeds a specified threshold, indicating potential network congestion or increased data output. Customization Guidance: Threshold: The default threshold is set based on typical network transmit patterns. Adjust this threshold according to your workload's data transfer requirements and expected network performance. Monitoring Period: A monitoring period of 5 minutes helps filter out transient spikes and focuses on sustained throughput issues. Adjust this period based on the criticality of your data transfer operations. Network Specificity: Tailor alerts for specific network interfaces or data streams that are critical to your operations, prioritizing those with high data transfer demands. Notification Frequency: Consider the frequency of this alert to balance responsiveness and noise. Adjust according to the criticality of the application(s) supported. Action: Upon triggering this alert, immediate actions include reviewing network configuration, analyzing data transfer patterns, and optimizing data output processes to alleviate potential congestion.

This alert detects health status degradation in your AWS Redshift environment. The alert is activated when the health status falls below a specified threshold, indicating potential operational issues or failures. Customization Guidance: Threshold: The default threshold is set to ensure prompt detection of health degradation. Adjust this threshold according to your cluster's operational requirements and expected performance standards. Monitoring Period: A monitoring period of 10 minutes helps filter out transient issues and focuses on sustained health status degradation. Adjust this period based on the criticality of your cluster's operations. Cluster Specificity: Tailor alerts for specific clusters based on their operational roles and criticality to your workloads. Notification Frequency: Consider the frequency of this alert to ensure timely notifications while minimizing unnecessary alerts. Action: Upon triggering this alert, immediate actions include reviewing system logs, analyzing performance metrics, and conducting a root cause analysis to address potential failures or issues.

This alert detects high CPU utilization in your AWS Redshift environment. The alert is activated when CPU utilization exceeds a specified threshold, indicating potential performance bottlenecks or resource constraints. Customization Guidance: Threshold: The default threshold is set based on typical CPU usage patterns. Adjust this threshold according to your workload's compute requirements and performance expectations. Monitoring Period: A monitoring period of 10 minutes helps filter out transient spikes and focuses on sustained CPU utilization. Adjust this period based on the criticality of your compute operations. Resource Allocation: Evaluate current resource allocation and ensure compute capacity aligns with workload demands to avoid potential bottlenecks. Notification Frequency: Consider the frequency of this alert to optimize the balance between responsiveness and noise. Adjust according to the criticality of the application(s) supported. Action: Upon triggering this alert, immediate actions include reviewing workload patterns, optimizing query execution, and considering scaling options to address increased compute demands.