In the ReposeFilter (formerly known as the PowerFilter), when you see the x-trace-request header come in, mark the logging context and stop taking the special action in the ReposeFilterChain (i.e. always log this info at trace).
Depending on how this is laid out, we may need to pass this data around (i.e. whether or not the request is "marked") the same way we pass around the UUID (a.k.a. GUID).
- Repose 9
- We no longer return timing data in the response when the x-trace-request header is sent in to the request.
- We start logging that timing data when the x-trace-request header is sent in to the request.
- Update "Troubleshooting" docs to reference the new method of determining this information.
- Update the log4j config that we ship with Repose to include an example of how to use this feature.
- Include examples of timing, Intrafilter logging, and the Apache wire logs.
- The x-trace-request header will be checked for upfront.
- We don't have to continue supporting turning on intrafilter logging for all requests.
- Repose 8
- We start logging Intrafilter logs and Apache wire logs when the x-trace-request header is sent in to the request.