End-to-end correlation across Logic Apps

Excellent Article on co-relating multiple logic apps which I find very useful. I am re-blogging this blog written by toon vanhoutte.

toon vanhoutte

When using a generic and decoupled integration design, your integrations span often multiple Logic Apps.  For troubleshooting purposes, it’s important to be able to correlate these separate Logic Apps with each other.  Recently, a new feature has been introduced to improve this.

Existing correlation functionality

  • Let’s create a Logic App with a simple request trigger.

Correlation-01

  • Invoke the Logic App.  In the run history details, you will notice a correlation id.

Correlation-02

  • Now, update the Logic App to call another Logic App.

Correlation-03

  • Invoke the parent Logic App.  In their run history details, you will notice that they both share the same id. This is because Logic Apps automatically adds the x-ms-client-tracking-id HTTP header, when calling the child Logic App.  If this header is present, that’s the value taken for the correlation id.

Correlation-04

  • Your client application can also provide this HTTP header, so a custom correlation id is used.

Correlation-05

  • This results in these…

View original post 566 more words

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s