FWIW - I'll share my logging:
I'm logging using a custom logger to capture policy execution - "PolicyExecLog" for ease of filtering.
Here is a snippet of my standard policy with the relevant logging bits:
I pair this up with a traffic logger defined as follows:
${requestId} | ${ssgnode.hostname} | ${request.http.header.x-forwarded-for} | ${request.http.method} | ${request.url} | ${response.http.status}
I'm considering the following:
- Adding a switch to dump out request and response bodies.
- Capturing a correlation id on the request. If it is not present, generating one on the gateway
- Adding a response header that carries the correlation id
Thanks,
Alejandro