Nowadays, developers are the same page that micro services is an approach for projects having quit complicated business with mayny service. To adapt and coordinate requests to services, api gateway mananagement is the most effective currently. However, inspectment is not evident specially in cloud system like azure. Let get down the business, I will intruct how to trace requests in api gateway management from my perspective.

All developers need are work on portal azure. to create a API gate managemen, I call it a day. Imagine that we have Api mananagement already interact with fumction app but it does not work, the request can not go to function app. First and foremost, I debug the Api mananagement.

We can send the message and inpect the log but no many information showed in this. I try out to another method that is trace request. To enable this, we have to set up in subcription.

Come back and trace the request, we see the details were devided into 4 part.

• Inbound - Shows the original request API Management received from the caller and the policies applied to the request. For example, if you added policies in Tutorial: Transform and protect your API, they'll appear here.

• Backend - Shows the requests API Management sent to the API backend and the response it received.

• Outbound - Shows the policies applied to the response before sending back to the caller.

• On error - Shows the errors that occurred during the processing of the request and the policies applied to the errors.

In additon, we can install extensions in vscode to debug clearly but need many steps to configutations. This extension is really helpful with some hard stuffs in api management like config policies, test locally, debug realtime,... However, our scope is just debug so tracing request is sufficient.