This alert triggers when the processor time for an AWS Directory Service domain controller exceeds 90% for a continuous period, indicating potential performance issues that may affect the directory service's responsiveness. Customization Guidance: Threshold: The alert is set to trigger at 90% processor time. Adjust this threshold if your environment can tolerate higher or lower processor usage. Controller Specificity: Focus on specific domain controllers that are critical to your operations. Notification Frequency: Ensure alerts are configured to notify in a timely manner without overwhelming the operations team. Action: Investigate the domain controller's workload and resource utilization. Consider optimizing the configuration, scaling resources, or distributing the load across additional controllers to reduce processor usage.

This alert triggers when the processor time for an AWS Directory Service domain controller exceeds 70% for a continuous period. Sustained high processor usage can be an early indicator of performance degradation. Customization Guidance: Threshold: The alert is set to trigger at 70% processor time. Adjust this based on your environment’s tolerance for high processor usage. Resource Allocation: Monitor resource allocation and consider scaling up resources if high processor usage persists. Notification Frequency: Set alerts to avoid overwhelming the team while ensuring prompt action. Action: Review the domain controller's performance metrics to identify any potential bottlenecks or inefficiencies. Adjust configurations or scale resources to optimize performance.

This alert triggers when the estimated queue delay (ATQ) for an AWS Directory Service domain controller exceeds 100 milliseconds, indicating potential delays in processing requests. Customization Guidance: Threshold: The alert is set to trigger at 100 ms queue delay. Adjust this threshold based on the acceptable delay in your environment. Controller Focus: Customize for specific domain controllers where latency is particularly critical. Notification Frequency: Configure to strike a balance between timely detection and alert fatigue. Action: Investigate the source of the delay, such as high load or network issues. Optimize the configuration or consider scaling resources to reduce queue delays.

This alert triggers when the estimated queue delay (ATQ) for an AWS Directory Service domain controller exceeds 50 milliseconds. Persistent queue delays can degrade overall service performance. Customization Guidance: Threshold: The alert is set to trigger at 50 ms queue delay. Adjust based on your environment's tolerance for latency. Queue Management: Monitor and optimize the handling of incoming requests to reduce delays. Notification Frequency: Ensure alerts are informative without being overwhelming. Action: Analyze the domain controller's workload to identify potential bottlenecks causing delays. Consider optimizing resource allocation or improving network performance to reduce latency.

This alert triggers when the number of TCP queries received per second by an AWS Directory Service domain controller exceeds 10,000, indicating a high volume of incoming requests that could strain resources. Customization Guidance: Threshold: The alert is set to trigger at 10,000 queries/sec. Adjust based on your environment's capacity to handle incoming queries. Traffic Management: Monitor and manage network traffic to ensure domain controllers are not overwhelmed. Notification Frequency: Balance between prompt detection and avoiding alert fatigue. Action: Review the volume of incoming queries to determine if they are expected or indicative of a potential issue such as a DDoS attack. Implement traffic management strategies or scale resources as needed.

This alert triggers when the number of recursive queries per second handled by an AWS Directory Service domain controller exceeds 100, potentially indicating inefficiencies in query resolution. Customization Guidance: Threshold: The alert is set to trigger at 100 recursive queries/sec. Adjust based on your environment's tolerance for query handling load. Query Optimization: Ensure that queries are optimized to minimize the need for recursion. Notification Frequency: Set to provide timely notifications without causing unnecessary disruptions. Action: Investigate the source of high recursive queries to identify inefficiencies or misconfigurations in the directory service or client applications. Optimize query handling to reduce recursion.

This alert triggers when the LDAP bind time for an AWS Directory Service domain controller exceeds 15 seconds, indicating potential delays in authentication processes. Customization Guidance: Threshold: The alert is set to trigger at 15 seconds bind time. Adjust based on acceptable authentication delay in your environment. Bind Time Monitoring: Regularly monitor bind times to ensure prompt user authentication. Notification Frequency: Configure alerts to ensure timely action without overwhelming the team. Action: Analyze the cause of the delay, such as network latency or server load. Optimize configurations or scale resources to reduce LDAP bind times.

This alert triggers when the average latency for I/O log writes on an AWS Directory Service domain controller exceeds 15 milliseconds, indicating potential issues with disk performance. Customization Guidance: Threshold: The alert is set to trigger at 15 ms latency. Adjust based on your environment’s tolerance for disk performance. Disk Performance Monitoring: Regularly monitor disk I/O performance to detect and address latency issues early. Notification Frequency: Ensure alerts are prompt and informative without causing alert fatigue. Action: Investigate the root cause of increased I/O latency, such as disk performance bottlenecks or high workload. Optimize disk usage or consider upgrading hardware to improve performance.

This alert triggers when the average latency for I/O database reads on an AWS Directory Service domain controller exceeds 50 milliseconds, potentially impacting directory service performance. Customization Guidance: Threshold: The alert is set to trigger at 50 ms latency. Adjust this based on your tolerance for read latency in directory operations. Read Latency Optimization: Focus on reducing read latency through optimization of database queries and I/O operations. Notification Frequency: Set to detect issues promptly while avoiding unnecessary notifications. Action: Investigate and address the causes of increased I/O read latency, such as inefficient queries, high server load, or disk performance issues. Optimize the configuration or scale resources to improve read performance.