/usr/share/doc/lire/dev-manual/ch01s03.html is in lire-devel-doc 2:2.1.1-2.1.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 | <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Log Analysis</title><meta name="generator" content="DocBook XSL Stylesheets V1.75.2"><link rel="home" href="index.html" title="Lire Developer's Manual"><link rel="up" href="ch01.html" title="Chapter 1. Architecture Overview"><link rel="prev" href="ch01s02.html" title="Log File Normalisation"><link rel="next" href="ch01s04.html" title="Report Generation"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Log Analysis</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch01s02.html">Prev</a> </td><th width="60%" align="center">Chapter 1. Architecture Overview</th><td width="20%" align="right"> <a accesskey="n" href="ch01s04.html">Next</a></td></tr></table><hr></div><div class="section" title="Log Analysis"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="sect:analysis"></a>Log Analysis</h2></div></div></div><p>After normalisation, comes the analysis process. The
analysis process responsability is to extracts, infers or
derives other information from the logged data. Since the
superservice's logged data is in a standard format, the
analysers are generic in the sense that they can operate for
all the superservice's supported log formats, if the
product's was clever enough to log the information required
by the analyser. The analysis process is shown in the <a class="xref" href="ch01s03.html#fig:flow-analysis" title="Figure 1.3. The Log Analysis Process">Figure 1.3, “The Log Analysis Process”</a> figure.
</p><div class="figure"><a name="fig:flow-analysis"></a><p class="title"><b>Figure 1.3. The Log Analysis Process</b></p><div class="figure-contents"><div align="center"><img src="flow-analysis.png" align="middle" alt="The Log Analysis Process"></div></div></div><br class="figure-break"><p>Since each analyser can add information to or create a
new DLF, each analyser will generate data according to
special kind of schemas.
</p><p><span class="application">Lire</span>'s framework include two kind of analysers. The
difference between the two resides in the mapping between
the source data and the new data they generate. Extended
analysers generate new data for each DLF record whereas
derived analysers are used when the new data doesn't have a
one-to-one mapping with the source data.
</p><p>The analysers produce data according to a data model
which is specified in other DLF schemas. There are
<em class="firstterm">extended</em> schemas and
<em class="firstterm">derived</em> schemas. An extended schema
simply adds new fields to the base superservice's schema.
For example, in the web superservice's schema, a lot of
information can be obtained from the referer field. From
this information, it is possible to guess the user's
browser, language or operating system. Those fields are
specified in the <span class="type">www-referer</span> extended schema;
one analyser is responsible for extracting this information
from the referer field.
</p><p>But sometimes the analysis cannot just simply add
information to each event record, an altogether different
schema is needed then. For those cases, there is the derived
schema. An example of the use of such a schema in the
current Lire distribution is the analyser which creates user
sessions based on the logged client IP address and user
agent. This analyser defines the <span class="type">www-session</span>
derived schema.
</p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ch01s02.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="ch01.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="ch01s04.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Log File Normalisation </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Report Generation</td></tr></table></div></body></html>
|