-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New %codes for computing message forwarding delays #260
base: bag64a
Are you sure you want to change the base?
Changes from 25 commits
334d87a
f19be20
03361d8
98ccecb
b34e422
e843568
44b7842
fa1b0ad
330ef13
c410a1c
8a8da4b
380f33a
bfb0102
a4f5a99
e4fad62
38038ad
109de07
507ab43
38daef3
57fda97
a9c51e7
3b23fd3
0a19226
626598c
8865b6f
bf09e96
7b4134b
c0dd69b
7ab3b89
ed0be1a
88c458c
3fb4e85
ff53998
235e422
692aaf8
12d9909
55e55d7
9d3b7e5
6e9189f
d8af1f5
9dd2725
ba8d04b
b70587b
cfff89f
3317bda
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -4868,6 +4868,28 @@ DOC_START | |
values may significantly understate or exaggerate actual times. | ||
Do not use this measurement unless you know it works in your case. | ||
|
||
TODO: Reduce duplication?? | ||
XXX: Format. | ||
|
||
event_time{name}: Approximate time of the named event in <full seconds since epoch>.<fractional seconds> format. The following events are currently supported: | ||
|
||
rousskov marked this conversation as resolved.
Show resolved
Hide resolved
|
||
request_first_read: Squid starts working with an incoming HTTP or FTP request. This event is the first successful read event for the request. A successful request read event usually corresponds to the completion of a successful socket read(2) call (including a zero-size/EOF read), but it may also be associated with discovering the request in a buffer filled when reading an earlier request (on the same client-to-Squid connection), extracting request bytes from a completed TLS handshake with the client, etc. Client-to-Squid TCP connection acceptance and client-Squid TLS handshake (if any) happen earlier. REQMOD adaptation of read bytes (if any) happens later. Failed socket reads do not trigger this event (and usually result in transaction errors). | ||
|
||
request_last_read: The latest observed event in a series of successful request read events. See request_first_read event for the definition of a successful request read event. If the entire request was received in a single socket read(2), then this event is the same as request_first_read event. | ||
|
||
request_first_write: Squid starts delivering an HTTP or FTP request to an origin server or cache_peer. If Squid retries or re-forwards the request, then this event corresponds to the last such attempt. For a given forwarded request, this event is the first successful write event for the request. A successful request write event corresponds to the completion of a successful socket write(2) call. REQMOD adaptation of written bytes (if any), Squid-to-peer TCP connection establishment and Squid-peer TLS handshake (if any) happen earlier. Failed socket writes do not trigger this event (and usually result in request forwarding errors). | ||
|
||
request_last_write: The latest observed event in a series of successful request write events. See request_first_write event for the definition of a successful request write event. If the entire request was delivered in a single socket write(2), then this event is the same as request_first_write event. | ||
|
||
response_first_read: Squid starts working with an incoming HTTP or FTP response. If Squid retries or re-forwards the request, receiving multiple responses, then this event corresponds to the last such response. For a given response, this event is the first successful read event for the response. A successful response read event corresponds to the completion of a successful socket read(2) call (including a zero-size/EOF read). Squid-to-peer TCP connection establishment and Squid-peer TLS handshake (if any) happen earlier. RESPMOD adaptation of read bytes (if any) happens later. Failed socket reads do not trigger this event (and usually result in response processing errors). | ||
|
||
response_last_read: The latest observed event in a series of successful response read events. See response_first_read event for the definition of a successful response read event. If the entire response was received in a single socket read(2), then this event is the same as response_first_read event. | ||
|
||
response_first_write: Squid starts delivering an HTTP or FTP response to a client. This event is the first successful write event for the response. A successful response write event corresponds to the completion of a successful socket write(2) call. RESPMOD adaptation of written bytes (if any) happens earlier. Failed socket writes do not trigger this event (and usually result in transaction errors). | ||
|
||
response_last_write: The latest observed event in a series of successful response write events. See response_first_write event for the definition of a successful response write event. If the entire response was delivered in a single socket write(2), then this event is the same as response_first_write event. | ||
|
||
|
||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The PR implementation differs from the proposed definitions (for request_first_read/request_last_read):
We could simplify request_first_read/request_last_read calculation, ignoring parsing time and measuring them from ClientHttpRequest constructor. However, this approach would minimize request_first_read/request_last_read difference in some cases, concealing this useful information from the admin. |
||
Access Control related format codes: | ||
|
||
et Tag returned by external acl | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This change is out of scope - it fixes a build error.