How to perform end-to-end message failure tracking in Azure?
When an application is built with distributed Azure Integration services, it becomes essential to end-to-end track message request flow to detect failures and isolate faulty services. Traditionally, this is done manually by going through hundreds of failure logs in Log Analytics by the developers, which kills their productivity. Also, the Application Map feature in Application Insights provides an oversimplified version of the topology map of the application. For instance, tracking the complete data flow in Azure Durable Functions is impossible.
