This alert has detected an increase in the number of throttled requests in Azure Service Bus. The alert is activated when the number of throttled requests exceeds 20 for a continuous period of 5 minutes. Customization Guidance: Threshold: The default threshold is set at 20 throttled requests. Depending on your specific application needs and past performance data, this threshold may need adjustment. Applications requiring high transaction rates might need a lower threshold to detect issues earlier. Bus Specificity: Tailor alerts for different Service Bus namespaces based on their roles in your infrastructure. Critical namespaces 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 Service Bus status, reviewing Service Bus configuration changes, checking for any misconfigurations or fine tunings as per your service infrastructure capacity needs. Mitigating failures automatically can be done following best practices of using Service Bus health checks and monitoring.

This alert has detected an increase in the number of deadlettered messages in Azure Service Bus. The alert is activated when the number of deadlettered messages exceeds 20 for a continuous period of 5 minutes. Customization Guidance: Threshold: The default threshold is set at 20 deadlettered messages. Depending on your specific application needs and past performance data, this threshold may need adjustment. Applications requiring high transaction rates might need a lower threshold to detect issues earlier. Bus Specificity: Tailor alerts for different Service Bus namespaces based on their roles in your infrastructure. Critical namespaces 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 Service Bus status, reviewing Service Bus configuration changes, checking for any misconfigurations or fine tunings as per your service infrastructure capacity needs. Mitigating failures automatically can be done following best practices of using Service Bus health checks and monitoring.

This alert has detected an increase in the rate of user errors in incoming requests to Azure Service Bus. The alert is activated when the user error rate exceeds 10% for a continuous period of 5 minutes. 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 transaction rates might need a lower threshold to detect issues earlier. Bus Specificity: Tailor alerts for different Service Bus namespaces based on their roles in your infrastructure. Critical namespaces 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 Service Bus status, reviewing Service Bus configuration changes, checking for any misconfigurations or fine tunings as per your service infrastructure capacity needs. Mitigating failures automatically can be done following best practices of using Service Bus health checks and monitoring.