Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
V
varnish-cache
Project
Project
Details
Activity
Releases
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Commits
Open sidebar
varnishcache
varnish-cache
Commits
e726134e
Commit
e726134e
authored
Jan 16, 2015
by
Federico G. Schwindt
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Sync with reality
This updates the last oustanding document to 4.0
parent
872f5a96
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
23 additions
and
22 deletions
+23
-22
operation-logging.rst
doc/sphinx/users-guide/operation-logging.rst
+23
-22
No files found.
doc/sphinx/users-guide/operation-logging.rst
View file @
e726134e
...
...
@@ -20,13 +20,13 @@ is logging. `varnishlog` gives you the raw logs, everything that is
written to the logs. There are other clients that can access the logs as well, we'll show you
these later.
In the terminal window you started Varnish now type ``varnishlog
`` and
press enter.
In the terminal window you started Varnish now type ``varnishlog
-g raw``
and
press enter.
You'll see lines like these scrolling slowly by.::
0 CLI - Rd ping
0 CLI
- Wr 200
PONG 1273698726 1.0
0 CLI
- Rd ping
0 CLI
- Wr 200 19
PONG 1273698726 1.0
These is the Varnish master process checking up on the caching process
to see that everything is OK.
...
...
@@ -37,25 +37,24 @@ app.
You'll see lines like these.::
11 Sess
ionOpen c 127.0.0.1 58912 0.0.0.0:8080
11 ReqStart
c 127.0.0.1 58912 595005213
11 R
xRequest
c GET
11 R
xURL
c /
11 R
xProtocol
c HTTP/1.1
11 R
xHeader
c Host: localhost:8080
11 R
xHeader
c Connection: keep-alive
11 Sess
Open c 127.0.0.1 58912 :8080 0.0.0.0 8080 1273698726.933590 14
11 ReqStart
c 127.0.0.1 58912
11 R
eqMethod
c GET
11 R
eqURL
c /
11 R
eqProtocol
c HTTP/1.1
11 R
eqHeader
c Host: localhost:8080
11 R
eqHeader
c Connection: keep-alive
The first column is an arbitrary number, it identifies the
session. Lines with the same number are coming from the same session
and are being handled by the same thread. The second column is the
*tag* of the log message. All log entries are tagged with a tag
indicating what sort of activity is being logged. Tags starting with
'Rx' indicate Varnish is receiving data and 'Tx' indicates sending data.
transaction. Lines with the same number are coming from the same
transaction. The second column is the *tag* of the log message. All
log entries are tagged with a tag indicating what sort of activity is
being logged.
The third column tell us whether this is is data coming
or going to
t
he client ('c') or to/from the backend ('b'). The forth column is the
data
being logged.
The third column tell us whether this is is data coming
from or going
t
o the client ('c'), or the backend ('b'). The forth column is the data
being logged.
Now, you can filter quite a bit with `varnishlog`. The basic options we think you
want to know are:
...
...
@@ -67,9 +66,11 @@ want to know are:
'-c'
Same as '-b' but for client side traffic.
'-m tag\:regex'
Only list transactions where the tag matches a regular expression. If
it matches you will get the whole transaction.
'-g request'
Group transactions by request.
'-q query'
Only list transactions matching this query.
.. XXX:Maybe a couple of sample commands here? benc
...
...
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