Sling Log Tracer currently provides support for fine grained control of enabling logs for specific request. To make this log more accessible it would be useful to have a feature where the client can also fetch the logs from specific request over HTTP.
This feature would work like below
- Client sends an HTTP request with header Sling-Tracer-Record set to true
- Server includes a request id as part of Sling-Tracer-Request-Id response headers
- The logs in json format can then be fetched like http://localhost:4802/system/console/tracer/9b5b01f6-f269-47c3-a889-2dc8d4d7938f.json (see attached output. it includes following data for now. It can be extended as per need
- RequestProgressTracker logs
- JCR Queries made
- Request id is randomly generated
- The access to request log is via Web Console Plugin servlet hence its only accessible to admin user account
- The request data would only be recorded for those request which have the Sling-Tracer-Record header set. The data would be kept in memory for some time with the assumption that client would fetch it soon. After some time the data would expire
- This feature would need to explicitly enabled via config option
- The feature is somewhat similar to 'Recent Request' support. However it exposes a JSON rendition and only keeps the data for request where client requested that.
- For this feature dependency is added for Guava Cache to make use of space bound/expiring cache. We can to an extent use LinkedHashMap but given that Guava is now being used in Sling for Oak it makes sense to make use of its feature. If required can look into embedding minimum required set