/usr/share/doc/lire/dev-manual/go01.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 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 | <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Glossary</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="index.html" title="Lire Developer's Manual"><link rel="prev" href="ch25.html" title="Chapter 25. Source Tree Layout"></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">Glossary</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch25.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> </td></tr></table><hr></div><div class="glossary" title="Glossary"><div class="titlepage"><div><div><h2 class="title"><a name="id420884"></a>Glossary</h2></div></div></div><p>Definitions of particular terms used in <span class="application">Lire</span>.</p><dl><dt>DLF</dt><dd><p>See <a class="glosssee" href="go01.html#term:dlf">Distilled Log Format</a>.</p></dd><dt>Distilled Log Format</dt><dd><div class="example"><a name="ex:dns.dlf"></a><p class="title"><b>Example 3. DNS DLF Excerpts</b></p><div class="example-contents"><pre class="programlisting">
1010912574 10.0.0.2 121.68.134.195.in-addr.arpa PTR recurs
1010912574 10.0.0.2 121.68.134.195.in-addr.arpa PTR recurs
1010912592 10.0.0.2 120.67.123.212.in-addr.arpa PTR recurs
1010912600 10.0.0.2 207.7.178.212.in-addr.arpa PTR recurs
1010912600 10.0.0.2 tr16.kennisnet.nl A recurs
1010912616 10.0.0.2 120.67.123.212.in-addr.arpa PTR recurs
1010912630 10.0.0.2 207.7.178.212.rbl.maps.vix.com ANY recurs
1010912630 10.0.0.2 NLnet.nl ANY recurs
</pre></div></div><br class="example-break"><p>This is the generic log format used by <span class="application">Lire</span> to
normalise the log files from different products.
</p><p>Currenlty, this normalised log is a simple ASCII format
where each event is represented by one line. The information
about the event is represented by fields separated by
spaces. All non-printable ASCII characters are replaced by
<code class="constant">?</code>. Spaces in a field's value are
replaced by <code class="constant">_</code> (an underscore). Each
line must have the same number of fields. A <acronym class="acronym">DLF</acronym> file
doesn't contain any header information. <a class="xref" href="go01.html#ex:dns.dlf" title="Example 3. DNS DLF Excerpts">Example 3, “DNS DLF Excerpts”</a> shows an excerpt
of a DNS <acronym class="acronym">DLF</acronym> file.
</p><p>See Also <a class="glossseealso" href="go01.html#term:superservice">Superservice</a>, <a class="glossseealso" href="go01.html#term:dlf-schema">DLF Schema</a>.</p></dd><dt>DLF Schema</dt><dd><p>Information about the order of the fields in a <acronym class="acronym">DLF</acronym>
file, their types and what they represent is specified in
the DLF's schema. Schemas are defined in XML files using the
<span class="application">Lire</span> <acronym class="acronym">DLF</acronym> Schema Markup Language (LDSML). <span class="application">Lire</span>'s offers
an API (only in Perl for now) to programmatically access the
information of a schema.
</p><p>Log files of many different products can share a common
DLF schema that makes <span class="application">Lire</span>'s <a class="link" href="go01.html#term:report">reports</a> easily comparable.
</p></dd><dt>Report</dt><dd><p>A report is what is generated by <span class="application">Lire</span>. It consists of
several <a class="link" href="go01.html#term:subreport">subreports</a>.
Those subreports can be grouped into sections. The report is
computed from the <acronym class="acronym">DLF</acronym> file (and not the native log file)
based on a configuration file which describes the subreports
that make up the final report along with their parameters.
(Consult the <em class="citetitle"><span class="application">Lire</span> User's Manual</em> section <em class="citetitle">Customizing <span class="application">Lire</span></em> for more
information.)
</p></dd><dt>Service</dt><dd><p>Put simply, a service is a specific application that
produces log files. It is usually the case that one
application will be equivalent to one service. For example,
the <span class="type">mysql</span> service is used to process <span class="productname">MySQL</span>™'s
log files.
</p><p>But more precisely, a service is a specific log format.
For example, the <span class="type">common</span> service can be used for
all web servers that support the Common Log Format.
Similarly, the <span class="type">welf</span> service can be used to
process firewall log files written using WebTrends Enhanced
Log Format.
</p><p>In order to generate a <a class="link" href="go01.html#term:report">report</a> on it, the native log
will be converted to the appropriate <a class="link" href="go01.html#term:superservice">superservice</a>'s <a class="link" href="go01.html#term:dlf-schema"><acronym class="acronym">DLF</acronym> schema</a>
</p></dd><dt>Subreport</dt><dd><p>A subreport is a particular view on the <acronym class="acronym">DLF</acronym> log's
data. Subreports are defined in XML files using the <span class="application">Lire</span>
Report Specification Markup Language (LRSML). (Although it
defines subreports, it is called a Report Specification
because a report is made up out of several subreports.)
Example of a subreport would be <em class="citetitle">Requests by Hours of the
Day</em>.
</p><p>Subreports are defined for a particular <a class="link" href="go01.html#term:dlf-schema"><acronym class="acronym">DLF</acronym> schema</a>.
</p></dd><dt>Superservice</dt><dd><p>A superservice is a collection of services that share
the same <a class="link" href="go01.html#term:dlf-schema"><acronym class="acronym">DLF</acronym> schema</a>
and <a class="link" href="go01.html#term:report">report</a>. It is used to
group together applications (<a class="link" href="go01.html#term:service">services</a>) that offer the
same kind of functionality.
</p><p><span class="application">Lire</span> currently supports eight superservices: database,
dns, email, firewall, ftp, print, proxy, and www.
</p></dd></dl></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ch25.html">Prev</a> </td><td width="20%" align="center"> </td><td width="40%" align="right"> </td></tr><tr><td width="40%" align="left" valign="top">Chapter 25. Source Tree Layout </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> </td></tr></table></div></body></html>
|