Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
Engine 2.3.10
-
None
Description
The Sling Engine web console configuration printer currently exposes all the Filter services that are used by the Sling engine.
It would be great if we cold expose usage and timing information about those filters as well to see which filters attribute the most to request processing.
At the same time internal filter handling can be improved to better abstract "holding" Filter services and leverage usage functionality such as said timing and tracking but also future requirements such as providing capabilities to not call filters unless some condition is met (e.g. only call a filter on certain resource types or paths)