Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 318264 - Stats handler should measure dispatch latency
Summary: Stats handler should measure dispatch latency
Status: CLOSED MOVED
Alias: None
Product: Jetty
Classification: RT
Component: server (show other bugs)
Version: 7.1.0   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: 7.1.x   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-28 20:21 EDT by Greg Wilkins CLA
Modified: 2016-02-16 18:41 EST (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Greg Wilkins CLA 2010-06-28 20:21:59 EDT
The stats handler should measure the ave,max and stddev of the time from when the request is first received by the connector until the time it is first seen by the stats handler.

It currently has the request timestamp, so it has this information available.


However, there is a small complication.  The request.setTimestamp(long) method is called in two places:

HttpConnection$RequestHandler.startRequest - when the request line is first parsed.

HttpConnection.handleRequest -> Connection.customizeRequest  - which is called after the request is dispatched. 

I think the second of these should be removed, as it will only be nano seconds before the request is handed to the stats server.

The first of these is after the request is dispatched, but then all handling in Jetty is dispatched - so it will do for now... perhaps we can eventually replace it with a timestamp set on the endpoint representing the last dispatched time.  Or maybe we have both?
Comment 1 Jesse McConnell CLA 2016-02-16 18:41:48 EST
https://github.com/eclipse/jetty.project/issues/87