You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The VSL transaction hierarchy illustrates the meaning of transaction levels. These levels can be used within the VSL query syntax.
However, the output cannot be filtered based on the transaction hierarchy.
This issue is a feature request that introduces the -l parameter for varnishlog, varnishtop, and varnishncsa. This parameter allows users to filter output based on transaction levels.
This example will look for ESI subrequests that took more than 2 seconds to load. The URL is returned, but instead of returning the URL for all linked transactions, only the level 2 transaction is returned.
In this hypothetical case, the URL of the ESI subrequest would be returned.
The syntax could also be a bit more flexible and allow ranges to be used:
varnishlog -g request -l 1-3
varnishlog -g request -l 2+
varnishlog -g request -l 3-
If session grouping is used, the level 1 transaction refer to the session, and not the request.
This -l parameter could conflict with -c and -b. If this featured has a chance of being implemented, we need to decide if -l has the precedence over -c and -b, or vice-versa.
Thoughts?
The text was updated successfully, but these errors were encountered:
The VSL transaction hierarchy illustrates the meaning of transaction levels. These levels can be used within the VSL query syntax.
However, the output cannot be filtered based on the transaction hierarchy.
This issue is a feature request that introduces the
-l
parameter forvarnishlog
,varnishtop
, andvarnishncsa
. This parameter allows users to filter output based on transaction levels.Here's a first example of this syntax:
This example will look for ESI subrequests that took more than 2 seconds to load. The URL is returned, but instead of returning the URL for all linked transactions, only the level 2 transaction is returned.
In this hypothetical case, the URL of the ESI subrequest would be returned.
The syntax could also be a bit more flexible and allow ranges to be used:
varnishlog -g request -l 1-3
varnishlog -g request -l 2+
varnishlog -g request -l 3-
If session grouping is used, the level 1 transaction refer to the session, and not the request.
This
-l
parameter could conflict with-c
and-b
. If this featured has a chance of being implemented, we need to decide if-l
has the precedence over-c
and-b
, or vice-versa.Thoughts?
The text was updated successfully, but these errors were encountered: