This has been sitting on my hard drive since last year. I have now
managed to give it some documentation and release it. I'm using it
myself and it really makes a difference sometimes. I'm looking for
some feedback on the project before I announce it somewhere else.
If there is sufficient interest, I'll also finish the queue management
support it's supposed to have. :)
Screenshots (pretty!):
http://duncanthrax.net/exilog/screenshots/
Download:
http://duncanthrax.net/exilog/
Read the docs to find out what it can do. Pasted below for your
convinience.
Exilog - Central logging and reporting tool for Exim
----------------------------------------------------
Author: Tom Kistner <tom@???>
Introduction
------------
Exilog is a tool to centralize and visualize Exim logs
across multiple Exim servers. It is used in addition to
Exim's standard or syslog logging. It does not require
changing Exim or its logging style (In fact you don't
even need to restart your Exim(s) to install Exilog).
Exilog is SQL-based and requires
- An SQL Server (mysql and postgres are supported)
- An HTTP Server with CGI support (Apache comes to mind)
- Perl and its DBD/DBI SQL Database modules for the
selected database.
- A modern browser (recent Mozilla, Firefox, IE5/6, Safari)
Target Audience
---------------
Postmasters who want to be able to troubleshoot email
delivery across their Exim installations, no matter if
used as relays or backend IMAP and POP toasters.
Postmasters who want to offload support grungework to
staff who is less proficient with grep, sed and awk.
Features
--------
Search for addresses, hosts (names and IP addresses),
messages IDs and ident strings.
Filter by event types: Arrivals, Deliveries, Deferrals,
Errors, Rejects and messages that are still on-queue.
Filter by time range, servers and server groups.
See basic host statistics, message sizes, message transfer
times.
Point-and-click on message IDs, IP addresses, hostnames to
get different filtering results.
Track messages across servers by header message ID.
Installation
------------
An Exilog installation consist of three parts:
1) The database holding the log information.
2) The web interface.
3) The agents on the Exim servers.
These parts can reside on different machines, or all be
on the same machine. For best results, the database and
web interface should be on the same physical box, however.
1) Installing the database.
Select if you want to use MySQL or Postgres. MySQL is
somehow preferred since its default case insensitivy
is better suited for the job.
Create a database using the respective SQL scripts from
/doc. For postgres, you might have to slightly edit the
script to change the 'exilog' user name (or create the
'exilog' user first).
If necessary, create a database user that has
full rights on the new database.
Make sure the database is reachable by TCP/IP from each
of your Exim servers.
2) Installing the Web Interface.
Untar the exilog distribution somewhere where your HTTP
server can reach it (/var/www/localhost/htdocs/exilog ...
you get the idea).
Edit the exilog.conf file. It is fully commented. Then
return to this document.
exilog_cgi.pl is the web interface. Set it up as
DirectoryIndex if you like.
Optionally, set up access controls. You should also deny
read access to exilog.conf from HTTP clients.
Now open your browser and open exilog_cgi.pl. If you see
the "Messages" tab you are fine.
Now we need to feed some data into the database.
3) Installing the Exim server agent(s).
You'll need to deploy one Exilog agent on each exim server
you run.
For each server, untar the Exilog distribution
somewhere, overwrite the vanilla exilog.conf with the one
you edited in step 2, then open it and tweak the "agent"
section to match the server you are installing it on.
Also tweak the SQL section to include host and port definitions
of your SQL server so the agent knows where to connect to.
Then run ./exilog_agent.pl as root. You might want to include
a start/stop procedure for the agent in your Exim rc file. It
needs to be run from the ./ CWD since otherwise Perl won't
find its modules.
Sending SIGTERM to the agent parent process will make it
cleanly quit, including all of its children.
When the agent is started, it will pump the current log file
into the database (this can take a while), then tail it. It
will automatically detect log rotation and re-open the file
if necessary.
Done! Report bugs and suggestions to me.
Tom Kistner
<tom@???>
June 2005
