This alert has detected an increase in the number of 5xx errors. The alert is activated when the number of 5xx errors is above a specified threshold for a continuous period. Customization Guidance: Threshold: The default threshold is set at 0. Depending on your specific application needs and past performance data, this threshold may need adjustment. Applications with critical operations 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 APIs based on their roles in your infrastructure. Critical APIs 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 gateway request duration. The alert is activated when the average gateway request duration exceeds a specified threshold for a continuous period. Customization Guidance: Threshold: The default threshold is set at 200 ms. 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 10 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 APIs based on their roles in your infrastructure. Critical APIs 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 failures 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 backend request duration. The alert is activated when the average backend request duration exceeds a specified threshold for a continuous period. Customization Guidance: Threshold: The default threshold is set at 200 ms. 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 10 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 APIs based on their roles in your infrastructure. Critical APIs 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 backend changes, checking for performance issues in backend services, and analyzing traffic patterns. Mitigating failures 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 number of other errors (non-4xx, non-5xx). The alert is activated when the number of such errors is above a specified threshold for a continuous period. Customization Guidance: Threshold: The default threshold is set at 0. Depending on your specific application needs and past performance data, this threshold may need adjustment. Applications with critical operations 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 APIs based on their roles in your infrastructure. Critical APIs 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 unexpected response codes, 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 number of 4xx errors. The alert is activated when the number of 4xx errors is above a specified threshold for a continuous period. Customization Guidance: Threshold: The default threshold is set at 0. Depending on your specific application needs and past performance data, this threshold may need adjustment. Applications with critical operations 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 APIs based on their roles in your infrastructure. Critical APIs 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 client-side 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 number of unauthorized requests. The alert is activated when the number of unauthorized (401) errors is above a specified threshold 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 requiring high security 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 unauthorized access attempts. 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 APIs based on their roles in your infrastructure. Critical APIs handling sensitive data 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 authentication issues, and analyzing traffic patterns. Mitigating unauthorized access attempts automatically can be done following best practices of using authentication mechanisms, rate limiting, and IP whitelisting.