why trace doesn't show header set in service call out policy

[#1]

Hi Devs,

So I noticed if there is any header being set in service callout, it is not visible in APigee trace and during troubleshooting we have to rely on application logs from the application Apigee is calling, to see proper header was sent by Apigee or not. To me it seems like an enhancement request. Please share your observations or may be I am missing something here ?

[#2]

I found another links thread where this issue is raised;

https://community.apigee.com/articles/2331/how-do-i-create-a-request-message-for-a-service-ca.html

[#3 · Accepted solution]

The response from your service callout is not automatically added to the response.

The trace Today does not do a good job of showing the request/response pipeline of the service called from the callout policy. That can be a good enhancement to trace!

The way to check the headers (and rest of the response from service callout) and use them in the flow (add them to your actual response, log them to analytics etc etc), you have to use ExtractVariables policy on the response object the service callout policy generates.

http://docs.apigee.com/api-services/reference/extract-variables-policy

The <source> of your extract variables should be same as the <response> in the service callout.

Example here: http://docs.apigee.com/api-services/cookbook/using-policy-composition