You may have noticed recently that any exception that you receive from either Event Hubs or Service Bus Messaging now contains a little bit more information. This is true for both AMQP and HTTP, which also means that whether you use one of our clients, or a third party client you will still be able to see the additional information.
Our customer service team routinely assists customers with issues that require a minimum set of data, which starts with the following:
- The affected namespace and entity name
- Date and time of the occurrence
- Any relevant tracking ids
We are happy to say that any exception you receive will now include the above information, as well as “FW Links.” These will provide you with a link to documentation for common fixes to the exception that you are seeing. If you cannot find a resolution to your particular issue, you won’t have to track down anything additional in order to create a ticket. This is great for both our customers as well as our customer service team, as we can immediately start diagnosing any issues without having to wait for more information. Above all, our goal is to find a solution as quickly as possible.
Below is an example of the new exception style as well as an old one for comparison sake. Please take note of the entity name, namespace, and FWLink in the new exception.
As always, we’re constantly iterating in order to make our product easier to use, so please let us know what you think!
- The Service Bus Team
One or more errors occurred. EventHub sending error. EventHub: EventHub(myEventHub)/32
The service was unable to process the request; please retry the operation. For more information on exception types and proper exception handling, please refer to http://go.microsoft.com/fwlink/?LinkId=761101 Reference:acac400b-eade-46fb-939b 027f9ff84492, TrackingId:f5e1ab94000000f10001a4be5733a67e_G55_B3, SystemTracker:myEventHubNamespace:eventhub:myEventHub~10823, Timestamp:5/12/2016 2:12:15 AM
Microsoft.ServiceBus.Messaging.MessagingException: The server was unable to process the request; please retry the operation. If the problem persists, please contact your Service Bus administrator and provide the tracking id. TrackingId:98cb664c-883c-47e2-b217-415f415a6828_G16,TimeStamp:7/10/2015 2:42:59 PM