Free to log software for linux

mod_log50x Apache module logs error 500 - 509 to logfiles. It enables you to log all error 50x status responses to logfiles.

How:

1. Either compile a apache module from the sources, or get a binary release.
2. Copy the module in the modules directory of your apache server.
3. Modify your httpd.conf to load the module:

LoadModule log50x_module modules/mod_log50x.so

4. Specify what errors should be logged in which logfile in your httpd.conf

Log50xFile /var/log/webserver50x.log
Log500File /var/log/webserver500.log
Log501File /var/log/webserver501.log
Log502File /var/log/webserver502.log
Log503File /var/log/webserver503.log
Log504File /var/log/webserver504.log
Log505File /var/log/webserver505.log
Log506File /var/log/webserver506.log
Log507File /var/log/webserver507.log
Log508File /var/log/webserver508.log
Log509File /var/log/webserver509.log

5. Restart your apache webserver


Details on the configuration options:

The Log50xFile specifies in which file all error in the range 500 - 509 should be logged.

The Log500File specifies in which file all error 500 should be logged.
The Log501File specifies in which file all error 501 should be logged.
etc.
The Log509File specifies in which file all error 509 should be logged.

It is possible to specify the same logfile multiple times, so this configuration results in all error 500 and 501 beeing logged in the same file.

Log500File /var/log/webserver500_501.log
Log501File /var/log/webserver500_501.log

When you specify the following configuration, then all error 500-509 are logged to the webserver50x logfile.

In addition to this, all error 500 are logged to the webserver500.log file.

Log50xFile /var/log/webserver50x.log
Log500File /var/log/webserver500.log

Simple Log is a small library that does logging very simply and requires you to do almost nothing (other than actually logging) to get log output to happen. Simple Log is much simpler to use than a logging framework, especially in terms of configuration.
It doesnt attempt to solve every logging problem in one package, but contains enough features to be a viable alternative for most applications that need logging. This tool will handle the logging needs of most small- to large-sized projects, but with an almost non-existent learning curve.
Enhancements:
- This release is primarily about the addition of log rolling (by time of day, file size, or custom strategy), the inclusion of a small but humorous user guide, the fixing of a raft of minor bugs, and the inclusion of a few other small features increasing flexibility.

Puppet::Log provides a log facility with an optional Tk display.
This class implements a log facility with an optional Tk display.
I
.e once the class is created, you can log messages in it, but the Tk display does no need to be created at the same time. You may invoke later only when you need it.
When the Tk display is not invoked, the log can be either printed on STDOUT or warned on STDERR (or stay hidden). But in any case, the log message will be stored in the class so that all log messages can be retrieved later by the user or by the Tk display when invoked.
Once the Tk display is invoked, it will be updated by new logs.
Constructor parameters:
- title: Title of the Tk log display (optional)
- name: Name of the log used when printing on STDOUT or STDERR (optional)
- how: Specifies what to do when a log is sent to the object (either print on STDOUT, warn on STDERR). By default the logs will not be printed or warned. (optional)
- help The argument may be a string or a sub reference. When the help menu is invoked, either the help string will be displayed in a Tk::Dialog box or the sub will be run. In this case it is the users responsability to provide a readable help from the sub. (See "help" in Tk::Multi::Manager for further details)
Puppet classes are a set of utility classes which can be used by any object. If you use directly the Puppet::*Body class, you get the plain functionnality. And if you use the Puppet::* class, you can get the same functionnality and a Tk Gui to manage it.
The basic idea is when you construct a Puppet::* object, you have all the functionnality of the object without the GUI. Then, when the need arises, you may (or the class may decide to) open the GUI of the object. On the other hand, if the need does not arise, you may create a lot of objects without cluttering your display.

Pax Logging is a consolidation effort that aims to make all existing logging APIs in the Java world available for OSGi developments, driven by a Log4J backend.
Each legacy API is loaded as its own bundle. The logging service can be reloaded at run-time.
Main features:
- Log4J driving the backend implementation.
- Log4J API supported.
- Jakarta Commons Logging API supported.
- Pax Logging Service implements the standard OSGi Log Service API.
- JDK Logging API support.
- Avalon Logger API support.
- SLF4J API support.
- Knopflerfish Log service support.

LoggedFS is a transparent fuse-filesystem which allows you to log every operation that happens in the backend filesystem.

Logs can be written to syslog, to a file, or to standard output. LoggedFS project comes with an XML configuration file in which you can choose exactly what you want to log.

You can add filters on users, operations (open, read, write, chown, chmod, etc.), filenames, and return codes.

Filenames filters are regular expressions. Since it is fuse-based, you dont need to change anything in your kernel or hard disk partition to use it.

PostgreSQL Table Log contains functions that allow you to log PostgreSQL table inserts, updates, and deletes into another table.
This can be used to recover the state of the logged table or to recover specific rows from a given time period.
Enhancements:
- This version now works with PostgreSQL versions 8.2 and later.
- Some warnings have been removed and the documentation was cleaned up.
- PGXS is now used for building from source.
- RPM packages are available.

Visitors is a very fast web log analyzer for Linux, Windows, and other Unix-like operating systems. It takes as input a web server log file, and outputs statistics in form of different reports. The design principles are very different compared to other software of the same type:
No installation required, can process up to 150,000 lines of log entries per second in fast computers (20MB/s with my log files average length).
Designed to be executed by the command line, output html and text reports. The text report can be used in pipe to less to check web stats from ssh.
Support for real time statistics with the Visitors Stream Mode introduced with version 0.3.
To specify the log format is not needed at all. Works out of box with apache and most other web servers with a standard log format (see the documentation for more information on the format).
Its a portable C program, can be compiled on many different systems. Binaries for Windows systems are in the Download section of this page.
The produced html report doesnt contain images or external CSS, is self-contained, you can send it by email to users.
Visitors is free software (and of course, freeware), under the terms of the GPL license. You dont need to pay to use it. Visitors is supported, if you want a custom version made directly by the original author for a modest price, contact me at antirez (at) invece.org. ISPs may take advantage of the high processing speed.
Main features:
- Requested pages.
- Requested images.
- Referers by hits and age.
- Unique visitors in each day.
- Page views per visit.
- Pages accessed by the Google crawler (and the date of googles last access on every page).
- Percentage of visits originated from Google searches for every day.
- Users navigation patterns (web trails).
- Keyphrases used in Google searches.
- User agents.
- Weekdays and Hours distributions of accesses.
- Weekdays/Hours combined bidimentional map.
- Month/Year combined bidimentional map.
- Visual path analysis with Graphviz.
- Operating systems, browsers and domains popularity.
- 404 errors.
Enhancements:
- This release adds an important bugfix in the unique visitors algorithm.
- The output is now nearer to reality (though unique visitors stats are always a guess without the use of a cookie).