Monitor alert: Throttling Health Event's title and cause needs to be more specific rather than word like "UserInitiated"
title: This storage account was throttled because it exceeded Azure Storage partition request per second, partition bandwidth, or IP scalability limits.,
Storage account throttling can be caused by busy storage partitions on the server side which is not related to customers' usage.
The "UserInitiated" wording in the health event cause would lead to misunderstanding of reaching service limit when customers' traffic is not there yet. Maybe we can change the wording to "ClientInitiated".
More specific alert cause can help both customers and support team to identify the issue efficiently.
• Instead of “UserInitiated”, we should change the wording to “Responding with Errors” or “ClientInitiated” in this scenario.
• We should not provide a list of possible throttling errors. If we are able to identify the specific type of throttling that occurred. We had better to directly provide customer-ready contents to the client side.
Filtering for solid Tunbridge Wells Taxi association? we've some wellbeing in UK air terminal exchange to and from Tunbridge Wells. Great Airport Transfers. No Delays, Punctual and Reliable Service. Capable Meet and Greet Service pronounced. Vehicles with unequivocal necessities.