loganalyzer/doc/manual.html
Rainer Gerhards 2e22324ee9 improved doc
2008-10-14 18:05:43 +02:00

62 lines
3.5 KiB
HTML

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html><head><title>phpLogCon documentation</title></head>
<body>
<h1>phpLogCon - Documentation</h1>
<p>The <b><a href="http://www.phplogcon.com/">phpLogCon</a>
project provides an easy to use but powerful front end for
searching, reviewing and analyzing network event data, including
syslog, windows event log and many other event sources.</b>
It focusses on the user-interface side of this project, so the
data itself needs to be gathered by another program,
for example the stock syslogd,
<a href="http://www.rsyslog.com">rsyslog</a> (often the distro's default syslogd),
<a href="http://www.winsyslog.com">WinSyslog</a> or
<a href="http://www.mwagent.com">MonitorWare Agent</a>.
PhpLogCon works equally well on Linux and
Windows. It is a free, GPLed open source application written mostly in php.
Data can be obtained from databases but also from plain text files, for
example those that are written by the syslgod.
<p><b>Follow the links below for the</b><br></p>
<ul>
<li><a href="basics.html">phpLogCon basics <b>Important - read this!</b></a></li>
<li><a href="searching.html">phpLogCon Search syntax</a></li>
<li><xa href="">phpLogCon configuration parameters</a></li>
<li><a href="textfiles.html">working with text log files</a></li>
<li><a href="windowsevent.html">using Windows Event Logs with phpLogCon</a></li>
<li><a href="troubleshoot.html">troubleshooting phpLogCon problems</a></li>
<li><a href="professional_services.html">phpLogCon professional services</a></li>
</ul>
<p><b>We have some in-depth papers on</b></p>
<ul>
<li><a href="build_from_repo.html">obtaining phpLogCon from the source repository</a></li>
<li><a href="http://www.mwagent.com/Common/en/Articles/setup_mwagent_webserverlogging_phplogcon_mysql.php">consolidating web server logs and viewing them with phpLogCon [Windows/Apache]</a></li>
<!--
<li><a href="install.html">installing phpLogCon</a></li>
<li><a href="debug.html">debug support in rsyslog</a></li>
-->
</ul>
<p><b>You can also browse the following online resources:</b></p>
<ul>
<li>the <a href="http://wiki.rsyslog.com/index.php/PhpLogCon">phpLogCon
wiki</a>, a community resource, part of the greater rsyslog wiki.
<li><a href="http://www.phplogcon.org/doc">phpLogCon online documentation (most current version only)</a></li>
<li><a href="http://kb.monitorware.com/phplogcon-f39.html">phpLogCon
discussion forum - use this for technical support</a></li>
<li><a href="http://www.rsyslog.com/Topic4.phtml">phpLogCon change log</b></a></li>
<li><a href="http://wiki.rsyslog.com/index.php/PhpLogCon_FAQ">phpLogCon FAQ</a></li>
<li><a href="http://www.monitorware.com/en/syslog-enabled-products/">syslog
device configuration guide</a> (off-site)</li>
<li><a href="http://www.rsyslog.com/doc-rsyslog_high_database_rate.html">writing massive amounts of syslog messages to a database via rsyslog</a> (this may be useful if you have lots of messages,
want to store them in databases but have performance issues doing so)</li>
</ul>
<p>And don't forget about the
<a href="http://lists.adiscon.net/mailman/listinfo/phplogcon">phplogcon
mailing list</a>. If you are interested in the "backstage" behind the overall idea that
phpLogCon contributes to, you may find
<a href="http://www.gerhards.net/rainer">Rainer</a>'s
<a href="http://blog.gerhards.net/">blog</a> an interesting read.
<p>Feedback is always welcome, but if you have a support question, please do not
mail the authors directly (<a href="free_support.html">why not?</a>).
</body></html>