All learning paths

Azure integration

Following one request through Logic Apps, Cosmos DB and Log Analytics by its correlation id, and the desktop tools that make each step visible.

4 articles · about 21 min of reading

0 of 4 read

Start with step 1

Tracing integration flows

  1. Step 1: AIS Runner: A Desktop GUI for Local Azure Logic Apps Standard DevelopmentAIS Runner is a Dioxus-based desktop app for local Azure Logic Apps Standard development — manage, run, debug, and compare workflows without leaving your dev environment.8 min
  2. Step 2: Your Logic Apps Are a Graph, and the Azure Portal Only Shows You a ListPast a dozen workflows, an Azure Logic Apps estate stops being a list and becomes a graph connected by Service Bus queues and Event Grid topics. Here is why the portal cannot show you that graph, and what to do about it.5 min
  3. Step 3: Following a Correlation ID Through Log Analytics Without Writing KQLA Log Analytics workspace holds the answer to where your integration flow stopped. Getting it out normally means a KQL query per table and knowing which column ties the steps together. It does not have to.4 min
  4. Step 4: How Far Did That Order Get? Tracing a Correlation ID Across Cosmos DBA customer says their order never arrived. You have a correlation id and an Azure Cosmos DB account with more containers than anyone remembers. Here is why the empty results matter more than the full ones.4 min