This alert has detected an increase in the total call errors exceeding 5%. The alert is activated when the percentage of call errors is above 5% for a continuous period. Customization Guidance: Threshold: The default threshold is set at 5%. Depending on your specific application needs and past performance data, this threshold may need adjustment. Applications requiring high reliability might need a lower threshold to detect issues earlier. Monitoring Period: A monitoring period of 10 minutes helps filter out transient spikes and focus on sustained issues. Adjust this period based on the criticality of your operations and the operational dynamics of your system. Please adapt it in the query as per your needs. API Specificity: Tailor alerts for different Cognitive Services APIs based on their roles in your infrastructure. Critical services handling high-stakes transactions may warrant more stringent monitoring. 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 of this alert, immediate actions include reviewing recent API changes, checking for backend issues, and analyzing traffic patterns. Mitigating failures automatically can be done following best practices of using retries, circuit breakers, and rate limiting.

This alert has detected an increase in the total call blocks exceeding 10%. The alert is activated when the percentage of call blocks is above 10% for a continuous period. Customization Guidance: Threshold: The default threshold is set at 10%. Depending on your specific application needs and past performance data, this threshold may need adjustment. Applications with high transaction volumes might need a lower threshold to detect issues earlier. Monitoring Period: A monitoring period of 10 minutes helps filter out transient spikes and focus on sustained issues. Adjust this period based on the criticality of your operations and the operational dynamics of your system. Please adapt it in the query as per your needs. API Specificity: Tailor alerts for different Cognitive Services APIs based on their roles in your infrastructure. Critical services handling high-stakes transactions may warrant more stringent monitoring. 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 of this alert, immediate actions include reviewing recent API changes, checking for backend issues, and analyzing traffic patterns. Mitigating failures automatically can be done following best practices of using retries, circuit breakers, and rate limiting.

This alert has detected an increase in the latency for operations exceeding 1000ms. The alert is activated when the average latency for operations is above 1000ms for a continuous period. Customization Guidance: Threshold: The default threshold is set at 1000ms. Depending on your specific application needs and past performance data, this threshold may need adjustment. Applications requiring low latency might need a lower threshold to detect issues earlier. Monitoring Period: A monitoring period of 5 minutes helps filter out transient spikes and focus on sustained latency issues. Adjust this period based on the criticality of your operations and the operational dynamics of your system. Please adapt it in the query as per your needs. API Specificity: Tailor alerts for different Cognitive Services APIs based on their roles in your infrastructure. Critical services handling high-stakes transactions may warrant more stringent monitoring. 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 of this alert, immediate actions include reviewing recent API changes, checking for backend performance issues, and analyzing traffic patterns. Mitigating latency issues automatically can be done following best practices of using performance optimization techniques such as caching, query optimization, and load balancing.

This alert has detected an increase in the total call errors. The alert is activated when the number of call errors exceeds a specified threshold for a continuous period. Customization Guidance: Threshold: The default threshold is set at 5 errors. Depending on your specific application needs and past performance data, this threshold may need adjustment. Applications requiring high reliability might need a lower threshold to detect issues earlier. Monitoring Period: A monitoring period of 10 minutes helps filter out transient spikes and focus on sustained issues. Adjust this period based on the criticality of your operations and the operational dynamics of your system. Please adapt it in the query as per your needs. API Specificity: Tailor alerts for different Cognitive Services APIs based on their roles in your infrastructure. Critical services handling high-stakes transactions may warrant more stringent monitoring. 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 of this alert, immediate actions include reviewing recent API changes, checking for backend issues, and analyzing traffic patterns. Mitigating failures automatically can be done following best practices of using retries, circuit breakers, and rate limiting.

This alert has detected an increase in the total blocked calls. The alert is activated when the number of blocked calls exceeds a specified threshold for a continuous period. Customization Guidance: Threshold: The default threshold is set at 5 blocked calls. Depending on your specific application needs and past performance data, this threshold may need adjustment. Applications with high transaction volumes might need a lower threshold to detect issues earlier. Monitoring Period: A monitoring period of 10 minutes helps filter out transient spikes and focus on sustained issues. Adjust this period based on the criticality of your operations and the operational dynamics of your system. Please adapt it in the query as per your needs. API Specificity: Tailor alerts for different Cognitive Services APIs based on their roles in your infrastructure. Critical services handling high-stakes transactions may warrant more stringent monitoring. 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 of this alert, immediate actions include reviewing recent API changes, checking for backend issues, and analyzing traffic patterns. Mitigating failures automatically can be done following best practices of using retries, circuit breakers, and rate limiting.