Free log files in mdbdata software for linux

Log Mine is a tool that produces reports on usage patterns on your Web site.
Web server log files are not just hit counters. They contain valuable information about the usage patterns of your website. Unforunately many web log analysis tools lay emphasis on telling you how many hits your site had or how many pages were seen and how many bytes were transferred.
A more usefull statistic would be which percentage of users came to your site went to a product information page, and which percentage of those users hit the checkout button, and which percentage actually completed their order. The trouble is the very nature of the web makes it nearly impossible to get accurate figures for such statistics.
However over periods of time, the errors present average out and it is possible to get a good indication of these ratios by properly mining the log file. That brings us back to square one, how do we get this information with traditional log analysers?
Traditional log analysers will produce weekly, monthly or daily charts for the usage of your site, but rarely do they allow you to create such charts for individual pages or referrrs - something very usefull if you run advertising campaigns on other sites.
Enter Log Mine. This new web log analyser / Mining tool will allow you to create just about any kind of report from the contents of your log file. Log Mine is not concerned about speed and it will be very greedy when it comes to taking up space on your hard disk/database but it will let you change your reporting without having to process gigabytes of log files each time.
Enhancements:
- Importing of Web server log files into the database was simplified.
- Multiple log files can now be processed at once.
- A bug in the monthly report was fixed.

klogview is a KDE real-time log file viewer, like tail -f. The main window contains any number of dockable log panels, with an arbitrary number of log sources in each of them.
Every log source can have a separate font color and style. Other features include filters, alerts, different encodings, and tray support.
Main features:
- Any number of dockable log panels
- Any number of log sources per log panel
- "File" log source
- "Process output" log source
- Configurable fonts and colors
- Filters and alerts
- Tray icon
Enhancements:
- Removed forced autoscroll
- Ability to reopen log files
- Ability to enable/disable log sources stop filter flag

logviewer is a GUI application for easy management of log files. It features page layout configuration, text filtering and date-time filtering for a logs name and for its pages, a date-time format variable, page selection and saving, and configurable file patterns and directories to analyze.
Main features:
- selection of configuration file on starting
- automatic load from configuration file of files list to show
- search configuration: files to show, directories to search files and files patterns to find (*.log, *log*.txt...)
- layout of showing files (show on pages)
- page configuration: number of characters per line and number of lines per page
- files list filtering based on "date-time from/date-time to" filters or text pattern filter
- pages-lines filtering based on "date-time from/date-time to" filters or text pattern filter
- date-time format configuration: standard sequence yyyymmddhhmmss, but with variables separators
- saving filtered or selected pages to new file
Installation
The installation is standard:
Source version:
- copy and decompression of package .tar.gz to installation directory
- ./configure
- make
- logviewer executable are created in src directory
(installation subdirectory)
Binary version:
- copy and decompression of package .tar.gz to installation directory
- decompressed file logviewer is the executable

LogServ is a module for NeoStats IRC Services that logs channel actions and messages to a log file for processing by channel log file parsers such as pisg, Onis, or MircStats.
LogServ can enable an IRC network to host the channel information Web pages commonly found for popular channels detailing information such as the number of people that have joined an IRC channel, or who spoke the most words.
Enhancements:
- Many internal code cleanups and bugfixes were done.
- This release is compatible with the latest alpha release of NeoStats 3.0.

Enas is a Perl script that can telnet to a Cisco router or switch, execute some command, and log the work on a file.

Easy Network Automated script can use a username/password or password/enable mode.

Log::Dispatch::Atom is a Perl module to log to an atom feed.

SYNOPSIS

use Log::Dispatch::Atom;

my $log = Log::Dispatch::Atom->new(
name => foo,
min_level => debug,
file => file.atom
);
$log->log_message( level => error, message => A problem happened );
$log->log_message( level => debug, message => Got Here );

This class implements logging backed by an Atom feed so that you can subscribe to the errors produced by your application.

You should not use this object directly, but should manage it via a Log::Dispatch object.

IMPLEMENTATION NOTES

In order to safely write to the log file, the entire file must be locked each time that an entry is logged. This probably makes it unsuitable for high volume log files.
The log file is opened and closed on each call to log_message().

METHODS

new()

Takes a hash of arguments. Returns a new Log::Dispatch::Atom object. The following parameters are used:

name [mandatory]

The name of the logging object.

min_level [mandatory]

The minimum logging level this object will accept. See Log::Dispatch for more information.

max_level [optional]

The maximum logging level this object will accept. See Log::Dispatch for more information. The default is the highest possible level (ie: no maximum).

file [mandatory]

Specifies the location of the file to read/write the feed from.

feed_id [optional]

Specifies the identity of the feed itself. Normally, this should be set to the published URI of the feed.
If not specified, it will be omitted, which is in violation of the Atom specification. For more information, see http://www.atomenabled.org/developers/syndication/#requiredFeedElements.

feed_title [optional]

The title of the feed. This should probably be set to the name of your application.

If not specified, it will be omitted, which is in violation of the Atom specification. For more information, see http://www.atomenabled.org/developers/syndication/#requiredFeedElements.
XXX This should probably just use the name parameter. What do you think? Let me know.

feed_author [optional]

The author details of a feed. This is specified as a hash reference, which must contain one or more of the three keys name, email and uri.

In order to create a valid Atom feed, you must either supply an author in every single entry (log message), or ensure that the feed itself has an author. The latter is probably the easier solution, so I recommend this parameter be supplied.

NB: The feed_* parameters will only be used when a new feed is being created. If you are creating a new object for an existing feed, they will be ignored.

log_message()

Takes a hash of arguments. Has no return value. The following parameters are used.

message [mandatory]

The actual log message.

level [mandatory]

The level of the message. See Log::Dispatch for a full list.

id [optional]

Each entry requires an id in order for the feed as a whole to be a valid Atom document. Its used by readers of Atom documents to determine whether or not an entry has been seen previously.

If not specified, this will default to an URL comprising the current time plus the pid plus the hostname plus a monotonically increasing integer. eg: tag:fred.example.com,2005-12-07:1133946771/20827/2. This should be good enough for a uniqueness test.

author [optional]

You can specify author details for an individual entry if desired. The author parameter is expected to be a hash reference, which must contain one or more of the keys name, email or uri.

genlogstatcoll is a generic collector to collect statistic data from log file delivered in via a syslog interface and provided via the AgentX interface through a SNMP daemon.

A syslog daemon (for instance syslog-ng) has to be configured to send relevant data (for instance the messages on the facility MAIL) to the genlogstatcoll too.

Considering the genlogstatcoll input interface is configured on 172.16.1.12, port 9514, this config line for syslog-ng will do the trick:

destination maillog { file("/var/log/mail/$YEAR/$MONTH/$DAY/mail.log"
create_dirs(yes) dir_perm(0755) owner("root") group("mail")
perm(0640)); udp("172.16.1.12" port(9514)); };

An SNMP daemon (for instance net-snmp 5.2.3) has to be configured to open the AgentX interface.

Considering the SNMP daemon should open the interface on 172.16.1.12, port 9161, these line in the snmpd.conf will do it:

master agentx
AgentXSocket 172.16.1.12:9161

Now, you can configure a facility to filter the input data, a SNMP oid to mount on and a couple of regexes, to count their matches in the log data.