Unable to see apigee response variables in bad gateway error timeout situation

[#1]

Every time apigee edge is throwing a bad gateway error. I see the below variables used for logging are returning blank values.

1-target.sent.end.timestamp

2-target.received.start.timestamp

This prohibits me in reaching to a conclusion whether its a proxy issue or a target server issue. Is there any other way where we can ensure that these variables log appropriate time stamps in case of 5 xx errors like bad gateway, time out situations?

Any help would be much appreciated.

[adas]

@chirantan those variables would usually be set if the request was sent to the target. Its possible that the connection to target is timing out in which case these variables are not set. The best thing to do in such cases is to open trace and see if the request is actually sent to the target and whether the 504 error happens in the Apigee layer or while connecting to the target. If you are on premise, you might want to check your message processor logs and even try to do a curl from the command line to your target server url.

If you are on the cloud, you would not be able to try those things so do a trace and share your findings. You might want to open a support ticket to troubleshoot the 594 errors if you do not think those are legitimate.