Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
U
unique-xids
Project
Project
Details
Activity
Releases
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
uplex-varnish
unique-xids
Commits
3673967c
Commit
3673967c
authored
Dec 19, 2011
by
Poul-Henning Kamp
Browse files
Options
Browse Files
Download
Plain Diff
Merge branch 'master' of
ssh://git.varnish-cache.org/git/varnish-cache
parents
4c1e8266
59a3b914
Changes
3
Show whitespace changes
Inline
Side-by-side
Showing
3 changed files
with
12 additions
and
17 deletions
+12
-17
varnishlog.rst
doc/sphinx/reference/varnishlog.rst
+2
-0
increasing_your_hitrate.rst
doc/sphinx/tutorial/increasing_your_hitrate.rst
+5
-3
logging.rst
doc/sphinx/tutorial/logging.rst
+5
-14
No files found.
doc/sphinx/reference/varnishlog.rst
View file @
3673967c
_reference-varnishlog:
==========
varnishlog
==========
...
...
doc/sphinx/tutorial/increasing_your_hitrate.rst
View file @
3673967c
...
...
@@ -31,9 +31,11 @@ Tool: varnishlog
~~~~~~~~~~~~~~~~
When you have identified the an URL which is frequently sent to the
backend you can use varnishlog to have a look at the whole request.
``varnishlog -c -m 'RxURL:^/foo/bar`` will give the whole (-o)
requests coming from the client (-c) matching /foo/bar.
backend you can use varnishlog to have a look at the request.
``varnishlog -c -m 'RxURL:^/foo/bar`` will show you the requests
coming from the client (-c) matching /foo/bar.
For more information on how varnishlog works please see :ref:`tutorial-logging`.
For extended diagnostics headers, see
http://www.varnish-cache.org/trac/wiki/VCLExampleHitMissHeader
...
...
doc/sphinx/tutorial/logging.rst
View file @
3673967c
.. _tutorial-logging:
Logging in Varnish
------------------
...
...
@@ -8,7 +9,7 @@ memory segment. When the end of the segment is reached we start over,
overwriting old data. This is much, much faster then logging to a file
and it doesn't require disk space.
The flip side is that i
s
you forget to have program actually write the
The flip side is that i
f
you forget to have program actually write the
logs to disk they will disappear.
varnishlog is one of the programs you can use to look at what Varnish
...
...
@@ -59,19 +60,9 @@ want to know are:
-c
Same as -b but for client side traffic.
-i tag
Only show lines with a certain tag. "varnishlog -i SessionOpen"
will only give you new sessions. Note that the tags are case
insensitive.
-I Regex
Filter the data through a regex and only show the matching lines. To
show all cookie headers coming from the clients:
``$ varnishlog -c -i RxHeader -I Cookie``
-o
Group log entries by request ID.
-m tag:regex
Only list transactions where the tag matches a regular expression. If
it matches you will get the whole transaction.
Now that Varnish seem to work OK it's time to put Varnish on port 80
while we tune it.
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment