<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
"http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head><meta http-equiv="content-type" content="text/html; charset=utf-8" />
<title>[12445] CalendarServer/trunk/doc/Admin/ExtendedLogItems.rst</title>
</head>
<body>
<style type="text/css"><!--
#msg dl.meta { border: 1px #006 solid; background: #369; padding: 6px; color: #fff; }
#msg dl.meta dt { float: left; width: 6em; font-weight: bold; }
#msg dt:after { content:':';}
#msg dl, #msg dt, #msg ul, #msg li, #header, #footer, #logmsg { font-family: verdana,arial,helvetica,sans-serif; font-size: 10pt; }
#msg dl a { font-weight: bold}
#msg dl a:link { color:#fc3; }
#msg dl a:active { color:#ff0; }
#msg dl a:visited { color:#cc6; }
h3 { font-family: verdana,arial,helvetica,sans-serif; font-size: 10pt; font-weight: bold; }
#msg pre { overflow: auto; background: #ffc; border: 1px #fa0 solid; padding: 6px; }
#logmsg { background: #ffc; border: 1px #fa0 solid; padding: 1em 1em 0 1em; }
#logmsg p, #logmsg pre, #logmsg blockquote { margin: 0 0 1em 0; }
#logmsg p, #logmsg li, #logmsg dt, #logmsg dd { line-height: 14pt; }
#logmsg h1, #logmsg h2, #logmsg h3, #logmsg h4, #logmsg h5, #logmsg h6 { margin: .5em 0; }
#logmsg h1:first-child, #logmsg h2:first-child, #logmsg h3:first-child, #logmsg h4:first-child, #logmsg h5:first-child, #logmsg h6:first-child { margin-top: 0; }
#logmsg ul, #logmsg ol { padding: 0; list-style-position: inside; margin: 0 0 0 1em; }
#logmsg ul { text-indent: -1em; padding-left: 1em; }#logmsg ol { text-indent: -1.5em; padding-left: 1.5em; }
#logmsg > ul, #logmsg > ol { margin: 0 0 1em 0; }
#logmsg pre { background: #eee; padding: 1em; }
#logmsg blockquote { border: 1px solid #fa0; border-left-width: 10px; padding: 1em 1em 0 1em; background: white;}
#logmsg dl { margin: 0; }
#logmsg dt { font-weight: bold; }
#logmsg dd { margin: 0; padding: 0 0 0.5em 0; }
#logmsg dd:before { content:'\00bb';}
#logmsg table { border-spacing: 0px; border-collapse: collapse; border-top: 4px solid #fa0; border-bottom: 1px solid #fa0; background: #fff; }
#logmsg table th { text-align: left; font-weight: normal; padding: 0.2em 0.5em; border-top: 1px dotted #fa0; }
#logmsg table td { text-align: right; border-top: 1px dotted #fa0; padding: 0.2em 0.5em; }
#logmsg table thead th { text-align: center; border-bottom: 1px solid #fa0; }
#logmsg table th.Corner { text-align: left; }
#logmsg hr { border: none 0; border-top: 2px dashed #fa0; height: 1px; }
#header, #footer { color: #fff; background: #636; border: 1px #300 solid; padding: 6px; }
#patch { width: 100%; }
#patch h4 {font-family: verdana,arial,helvetica,sans-serif;font-size:10pt;padding:8px;background:#369;color:#fff;margin:0;}
#patch .propset h4, #patch .binary h4 {margin:0;}
#patch pre {padding:0;line-height:1.2em;margin:0;}
#patch .diff {width:100%;background:#eee;padding: 0 0 10px 0;overflow:auto;}
#patch .propset .diff, #patch .binary .diff {padding:10px 0;}
#patch span {display:block;padding:0 10px;}
#patch .modfile, #patch .addfile, #patch .delfile, #patch .propset, #patch .binary, #patch .copfile {border:1px solid #ccc;margin:10px 0;}
#patch ins {background:#dfd;text-decoration:none;display:block;padding:0 10px;}
#patch del {background:#fdd;text-decoration:none;display:block;padding:0 10px;}
#patch .lines, .info {color:#888;background:#fff;}
--></style>
<div id="msg">
<dl class="meta">
<dt>Revision</dt> <dd><a href="http://trac.calendarserver.org//changeset/12445">12445</a></dd>
<dt>Author</dt> <dd>cdaboo@apple.com</dd>
<dt>Date</dt> <dd>2014-01-24 09:53:33 -0800 (Fri, 24 Jan 2014)</dd>
</dl>
<h3>Log Message</h3>
<pre>Add some missing items.</pre>
<h3>Modified Paths</h3>
<ul>
<li><a href="#CalendarServertrunkdocAdminExtendedLogItemsrst">CalendarServer/trunk/doc/Admin/ExtendedLogItems.rst</a></li>
</ul>
</div>
<div id="patch">
<h3>Diff</h3>
<a id="CalendarServertrunkdocAdminExtendedLogItemsrst"></a>
<div class="modfile"><h4>Modified: CalendarServer/trunk/doc/Admin/ExtendedLogItems.rst (12444 => 12445)</h4>
<pre class="diff"><span>
<span class="info">--- CalendarServer/trunk/doc/Admin/ExtendedLogItems.rst 2014-01-24 02:04:35 UTC (rev 12444)
+++ CalendarServer/trunk/doc/Admin/ExtendedLogItems.rst 2014-01-24 17:53:33 UTC (rev 12445)
</span><span class="lines">@@ -1,7 +1,8 @@
</span><span class="cx"> Apache-style Access Log Extensions
</span><span class="cx"> ==================================
</span><span class="cx">
</span><del>-If the administrator enables the EnableExtendedAccessLog config option, Calendar Server extends the Apache log file format it uses by:
</del><ins>+If the administrator enables the EnableExtendedAccessLog config option,
+Calendar Server extends the Apache log file format it uses by:
</ins><span class="cx">
</span><span class="cx"> * Adding a "sub-method" to the HTTP method field.
</span><span class="cx"> * Adding key-value pairs at the end of log lines.
</span><span class="lines">@@ -21,7 +22,8 @@
</span><span class="cx">
</span><span class="cx"> ``i``
</span><span class="cx">
</span><del>- the index number of the server instance emitting the log; corresponds to the slave number shown in process title.
</del><ins>+ the index number of the server instance emitting the log; corresponds
+ to the slave number shown in process title.
</ins><span class="cx">
</span><span class="cx"> ``t``
</span><span class="cx">
</span><span class="lines">@@ -65,27 +67,69 @@
</span><span class="cx">
</span><span class="cx"> ``itip.reply``
</span><span class="cx">
</span><del>- Either ``reply`` or ``cancel`` depending on...???
</del><ins>+ either ``reply`` or ``cancel`` depending on what action the attendee took
</ins><span class="cx">
</span><ins>+ ``itip.ischedule``
+
+ the number of iTIP iSchedule messages sent
+
</ins><span class="cx"> ``fwd``
</span><span class="cx">
</span><span class="cx"> the value of the X-Forwarded-For header, if present
</span><span class="cx">
</span><ins>+ ``cached``
+
+ indicates that the PROPFIND cache was used for the response.
+
</ins><span class="cx"> ``fb-cached``
</span><span class="cx">
</span><del>- When doing free-busy queries, this is the number of calendars queried for which free-busy info was already cached
</del><ins>+ when doing free-busy queries, this is the number of calendars queried for
+ which free-busy info was already cached
</ins><span class="cx">
</span><span class="cx"> ``fb-uncached``
</span><span class="cx">
</span><del>- When doing free-busy queries, this is the number of calendars queried for which free-busy info was NOT already cached
</del><ins>+ when doing free-busy queries, this is the number of calendars queried for
+ which free-busy info was NOT already cached
</ins><span class="cx">
</span><span class="cx"> ``cl``
</span><span class="cx">
</span><del>- Content length, in bytes
</del><ins>+ content length, in bytes
</ins><span class="cx">
</span><ins>+ ``create``
+
+ the number of resources to be created in a CRUD POST request
+
+ ``update``
+
+ the number of resources to be updated in a CRUD POST request
+
+ ``delete``
+
+ the number of resources to be deleted in a CRUD POST request
+
+ ``xpod``
+
+ the number of requests between server pods
+
+ ``sql-s``
+
+ the number of SQL statements executed during the request
+
+ ``sql-r``
+
+ the number of SQL rows returned during the request
+
+ ``sql-t``
+
+ the amount of time spent waiting for SQL statements to complete
+
+
</ins><span class="cx"> In the following example, we see a free-busy ``POST``
</span><span class="cx"> requesting availability for two users, which was handled by
</span><del>-instance ``1`` in 782.6i ms. This instance was only processing one request at the time this was logged (or=1). Of the two calendars targeted by the free-busy query, one already had free-busy info cached, while the other was not cached. (fb-cached=1, fb-uncached=1)
</del><ins>+instance ``1`` in 782.6i ms. This instance was only processing one request at
+the time this was logged (or=1). Of the two calendars targeted by the free-busy
+query, one already had free-busy info cached, while the other was not cached.
+(fb-cached=1, fb-uncached=1)
</ins><span class="cx">
</span><span class="cx"> ::
</span><span class="cx">
</span><span class="lines">@@ -94,12 +138,16 @@
</span><span class="cx">
</span><span class="cx"> **Fine-grained request time logging**
</span><span class="cx">
</span><del>-If the configuration key EnableExtendedTimingAccessLog is set to true, additional key-value pairs will be logged with each request. The overall request time "t" is broken into four phases, and the elapsed time for each phase is logged. The new keys representing the four request phases are:
</del><ins>+If the configuration key EnableExtendedTimingAccessLog is set to true, additional
+key-value pairs will be logged with each request. The overall request time "t" is
+broken into four phases, and the elapsed time for each phase is logged. The new
+keys representing the four request phases are:
</ins><span class="cx">
</span><span class="cx"> ``t-req-proc``
</span><span class="cx">
</span><del>- time elapsed from when a request object is created up until renderHTTP is about to be called.
- This is the overhead of parsing the request headers and locating the target resource.
</del><ins>+ time elapsed from when a request object is created up until renderHTTP is
+ about to be called. This is the overhead of parsing the request headers and
+ locating the target resource.
</ins><span class="cx">
</span><span class="cx"> ``t-resp-gen``
</span><span class="cx">
</span></span></pre>
</div>
</div>
</body>
</html>