Hi Team, Some time back I implemented Tracer [1] which simplifies enabling the logs for specific category at specific level and only for specific request. It provides a very fine level of control via config provided as part of HTTP request around how the logging should be performed for given category.
For e.g. determining what nodes are written for a given POST request can be simply done by including an extra request parameter "tracer" curl -D - -u admin:admin \ -d "./jcr:content/jcr:title=Summer Collection" \ -d ":name=summer-collection" \ -d "./jcr:primaryType=sling:Folder" \ -d "./jcr:content/jcr:primaryType=nt:unstructured" \ -d "tracers=oak-writes" \ http://localhost:8080/content/dam/ One can also specify actual categories as part of request param itself. For complete details refer to [1] Initially I submitted this as a pull request to Adobe ACS Tools. After using it for a while on few customer setups I realize that having it present out of the box in the product itself would be useful for developers in there day to day development also. Given that its a generic component it can be made part of some Sling bundle Not sure though on whats the best place to host this component. Should it be part of some new bundle or we add it to [2]. Thoughts? regards Chetan [1] https://github.com/Adobe-Consulting-Services/acs-aem-tools/pull/100 [2] https://github.com/apache/sling/tree/trunk/contrib/extensions/slf4j-mdc Chetan Mehrotra
