Azure-docs: Azure Service bus issue - unable to track Server errors to understand the reason

[ArenHarut]

We are having fair amount of server errors on all our service bus resources during a certain point in a day and we have not able to track those server errors.
According to this ticket it was not possible to check errors:
https://github.com/MicrosoftDocs/azure-docs/issues/13811

Just wanted to check if there are any updates on this issue. I was not able to get any clues about this in documentation.

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 234dca79-9576-7bfb-644a-ef486c9ca2f6
• Version Independent ID: a4d50a1a-4978-1506-77b9-efd12d6ea784
• Content: Azure Service Bus metrics in Azure Monitor - Azure Service Bus
• Content Source: articles/service-bus-messaging/service-bus-metrics-azure-monitor.md
• Service: service-bus-messaging
• GitHub Login: @axisc
• Microsoft Alias: aschhab

[ArenHarut]

https://stackoverflow.com/questions/50270009/azure-servicebus-high-amount-of-server-errors-in-metrics

[MayankBargali-MSFT]

@ArenHarut Service error means that the service was not able to process your message during that time. There can be multiple reasons for those server errors during that time for your service bus.

The document can only give you details about what does the server error means https://docs.microsoft.com/en-us/azure/service-bus-messaging/service-bus-metrics-azure-monitor#request-metrics but to know the exact cause of those errors you can always create a support ticket via Azure support.

If you are not able to create the support ticket then please send an email with the subject line “Attn:Mayank” to AzCommunity[at]Microsoft[dot]com referencing this thread along with the service bus name and timeframe (in UTC) when you have observed the internal error.

[ArenHarut]

@MayankBargali-MSFT thanks for your prompt response. I will continue communication via email. I have already sent you an email with the specific information that you mentioned to [email protected]. Please let me know that you received the email.

[ArenHarut]

@MayankBargali-MSFT I also checked Service Health about maintainance notice or alerts and there was only one for August 10.
https://portal.azure.com/#blade/Microsoft_Azure_Health/AzureHealthBrowseBlade/healthHistory/trackingId/8_4Y-V88

But we received Server errors on August 7 and 11, too.

[MayankBargali-MSFT]

@ArenHarut I have sent you a detailed analysis from backend logs. In nutshell, there was service updates on the scale unit where your namespace is hosted. These updates are pushed from the product group from time to time to improve the service.

There will be no notification sent to the customers for these service updates but to minimize the impact in your application please make sure that retry logic is handled in the code with exponential back-off so that intermittent issues/service updates like this should not affect your workflow: https://docs.microsoft.com/en-us/azure/architecture/best-practices/retry-service-specific#service-bus-retry-guidelines

We also recommend you to create Service Bus partitioned entities, in cases wherein there are issues with the service bus infra or upgrade, it helps avoid having a single point of failure.

[ArenHarut]

@MayankBargali-MSFT thank you so much for your answer in the email. I will pass this to our Dev team, too.
Closing this ticket.