{=
  include("docs.util");
  start_docs_page(docs.technical_manual.page_titles.lfnodes);
=}

<p><b>The log.fields node of a profile contains one subnode per log field. The layout of each field node is:</b>
<br>
<br/>
<a href="#label">label</a><br/>
<a href="#type">type</a><br/>
<a href="#index">index</a><br/>
<a href="#subindex">subindex</a><br/>
<a href="#hierarchy_dividers">hierarchy_dividers</a><br/>
<a href="#left_to_right">left_to_right</a><br/>
<a href="#leading_divider">leading_divider</a><br/>
<a href="#case_sensitive">case_sensitive</a><br/>
<a href="#derived_from_1">derived_from_1</a><br/>
<a href="#derived_from_2">derived_from_2</a><br/>
<br>
<br />


<TABLE BORDER CELLPADDING=10 Rules=all frame=box>
<a name="label"></a>
<TR><TH COLSPAN=2 bgcolor="#CCCC99">label</TH></TR>
<TR><TD>Type:</TD> <TD>string</TD></TR>
<TR><TD>Values:</TD><TD>Unique log field label.</TD></TR>
<tr><td>Default value:</td><td>-</td></tr>
<tr><td>Relevant:</td><td>always</td></tr>
<tr><td>Notes: </td><td></td></tr>
</table>
<br>
<br />
<TABLE BORDER CELLPADDING=10 Rules=all frame=box>
<a name="type"></a>
<TR><TH COLSPAN=2 bgcolor="#CCCC99">type</TH></TR>
<TR><TD>Type:</TD> <TD>string</TD></TR>
<TR><TD>Values:</TD><TD>agent <br/>date <br/> date_time <br/> flat <br/> hierarchical <br/> host <br/> page <br/> response <br/> size <br/> time <br/> URL</TD></TR>
<tr><td>Default value:</td><td>flat</td></tr>
<tr><td>Relevant:</td><td>always</td></tr>
<tr><td>Notes: </td><td></td></tr>
</table>
<br>
<br />
<TABLE BORDER CELLPADDING=10 Rules=all frame=box>
<a name="index"></a>
<TR><TH COLSPAN=2 bgcolor="#CCCC99">index</TH></TR>
<TR><TD>Type:</TD> <TD>int</TD></TR>
<TR><TD>Values:</TD><TD>-</TD></TR>
<tr><td>Default value:</td><td>0</td></tr>
<tr><td>Relevant:</td><td>always</td></tr>
<tr><td>Notes: </td><td>Technically, index/subindex are relevant only when doing index/subindex style parsing, but it's difficult to determine automatically if that is occuring, hence they are always relevant.</td></tr>
</table>
<br>
<br />
<TABLE BORDER CELLPADDING=10 Rules=all frame=box>
<a name="subindex"></a>
<TR><TH COLSPAN=2 bgcolor="#CCCC99">subindex</TH></TR>
<TR><TD>Type:</TD> <TD>int</TD></TR>
<TR><TD>Values:</TD><TD>-</TD></TR>
<tr><td>Default value:</td><td>0</td></tr>
<tr><td>Relevant:</td><td>always</td></tr>
<tr><td>Notes: </td><td>Technically, index/subindex are relevant only when doing index/subindex style parsing, but it's difficult to determine automatically if that is occuring, hence they are always relevant.</td></tr>
</table>
<br>
<br />
<TABLE BORDER CELLPADDING=10 Rules=all frame=box>
<a name="hierarchy_dividers"></a>
<TR><TH COLSPAN=2 bgcolor="#CCCC99">hierarchy_dividers</TH></TR>
<TR><TD>Type:</TD> <TD>string</TD></TR>
<TR><TD>Values:</TD><TD>A string with length <=2.</TD></TR>
<tr><td>Default value:</td><td>/</td></tr>
<tr><td>Relevant:</td><td>Only relevant for fields with type="hierarchical".</td></tr>
<tr><td>Notes: </td><td>The hierarchy_dividers node may exist in existing profiles or at profile creation time, even if the type is not "hierarchical", in this case we can ignore or delete the node!</td></tr>
</table>
<br>
<br />
<TABLE BORDER CELLPADDING=10 Rules=all frame=box>
<a name="left_to_right"></a>
<TR><TH COLSPAN=2 bgcolor="#CCCC99">left_to_right</TH></TR>
<TR><TD>Type:</TD> <TD>boo|</TD></TR>
<TR><TD>Values:</TD><TD>boo|</TD></TR>
<tr><td>Default value:</td><td>true</td></tr>
<tr><td>Relevant:</td><td>Only relevant for fields with type="hierarchical".</td></tr>
<tr><td>Notes: </td><td>The left_to_right node may exist in existing profiles or at profile creation time, even if the type is not "hierarchical", in this case we can ignore or delete the node!</td></tr>
</table>
<br>
<br />
<TABLE BORDER CELLPADDING=10 Rules=all frame=box>
<a name="leading_divider"></a>
<TR><TH COLSPAN=2 bgcolor="#CCCC99">leading_divider</TH></TR>
<TR><TD>Type:</TD> <TD>boo|</TD></TR>
<TR><TD>Values:</TD><TD>-</TD></TR>
<tr><td>Default value:</td><td>true</td></tr>
<tr><td>Relevant:</td><td>Only relevant for fields with type="hierarchical".</td></tr>
<tr><td>Notes: </td><td>The leading_divider node may exist in existing profiles or at profile creation time, even if the type is not "hierarchical", in this case we can ignore or delete the node!</td></tr>
</table>
<br>
<br />
<TABLE BORDER CELLPADDING=10 Rules=all frame=box>
<a name="case_sensitive"></a>
<TR><TH COLSPAN=2 bgcolor="#CCCC99">case_sensitive</TH></TR>
<TR><TD>Type:</TD> <TD>boo|</TD></TR>
<TR><TD>Values:</TD><TD>-</TD></TR>
<tr><td>Default value:</td><td>false</td></tr>
<tr><td>Relevant:</td><td>always</td></tr>
<tr><td>Notes: </td><td></td></tr>
</table>
<br>
<br />
<TABLE BORDER CELLPADDING=10 Rules=all frame=box>
<a name="derived_from_1"></a>
<TR><TH COLSPAN=2 bgcolor="#CCCC99">derived_from_1</TH></TR>
<TR><TD>Type:</TD> <TD>string</TD></TR>
<TR><TD>Values:</TD><TD>-</TD></TR>
<tr><td>Default value:</td><td>-</td></tr>
<tr><td>Relevant:</td><td>Only if the node exists and is not empty.</td></tr>
<tr><td>Notes: </td><td>Derived fields are automatically created by the C++. A log field which contains a derived_from_1 node should not be editable but only displayed in the GUI.</td></tr>
</table>
<br>
<br />
<TABLE BORDER CELLPADDING=10 Rules=all frame=box>
<a name="derived_from_2"></a>
<TR><TH COLSPAN=2 bgcolor="#CCCC99">derived_from_2</TH></TR>
<TR><TD>Type:</TD> <TD>string</TD></TR>
<TR><TD>Values:</TD><TD>-</TD></TR>
<tr><td>Default value:</td><td>-</td></tr>
<tr><td>Relevant:</td><td>Only if the node exists and is not empty.</td></tr>
<tr><td>Notes: </td><td>Derived fields are automatically created by the C++. A log field which contains a derived_from_2 node should not be editable but only displayed in the GUI.</td></tr>
</table>







{= end_docs_page() =}