I'd like to go ahead and commit the code attached to SLING-1476 with some additions to start pushing forward on adding JMX instrumentation to Sling. I'm trying to decide whether or not this should be placed into the engine bundle or as a separate bundle. This particular bit of JMX support can go in either place, but I'd like to use it to establish some best practices around JMX instrumentation within Sling. While a simple Filter can be used to track request counts (and min/max/average times), that may not always be the case, e.g. instrumenting the servlet resolver or the JCR resource resolver.
So the question is... do we add a separate instrumentation bundle just for things which can be instrumented externally to the bundle or start establishing the idea that each bundle is responsible for providing its own instrumentation? WDYT? Justin
