Details
-
Improvement
-
Status: Closed
-
Minor
-
Resolution: Fixed
-
Engine 2.0.4
-
None
-
None
Description
The SlingRequestProgressTracker messages contain useful timing information, structuring them a bit more would allow for parsing them to generate other representations.
Here's an example of the current info (from http://localhost:8888/system/console/requests):
0 (2009-10-07 11:10:30) Starting Request Processing
0 (2009-10-07 11:10:30) Method=GET, PathInfo=/index.html
0 (2009-10-07 11:10:30) Starting ResourceResolution
6 (2009-10-07 11:10:30) URI=/index.html resolves to Resource=JcrNodeResource, type=nt:file, superType=null, path=/index.html, elapsed = 6ms
6 (2009-10-07 11:10:30) Resource Path Info: SlingRequestPathInfo: path='/index.html', selectorString='null', extension='null', suffix='null'
6 (2009-10-07 11:10:30) Starting ServletResolution
6 (2009-10-07 11:10:30) Starting resolveServlet(JcrNodeResource, type=nt:file, superType=null, path=/index.html)
6 (2009-10-07 11:10:30) Using servlet org.apache.sling.servlets.get.DefaultGetServlet, elapsed = 0ms
6 (2009-10-07 11:10:30) URI=/index.html handled by Servlet=org.apache.sling.servlets.get.DefaultGetServlet, elapsed = 0ms
6 (2009-10-07 11:10:30) Applying request filters
6 (2009-10-07 11:10:30) Calling filter: org.apache.sling.engine.impl.debug.RequestProgressTrackerLogFilter
6 (2009-10-07 11:10:30) Starting org.apache.sling.servlets.get.DefaultGetServlet#0
6 (2009-10-07 11:10:30) Using org.apache.sling.servlets.get.impl.helpers.StreamRendererServlet to render for extension=null
7 (2009-10-07 11:10:30) org.apache.sling.servlets.get.DefaultGetServlet#0, elapsed = 1ms
7 (2009-10-07 11:10:30) Request Processing ends, elapsed = 7ms
Attachments
Issue Links
- is related to
-
SLING-1000 Web console plugin to display recent requests
- Closed