Windows multi-client logging solution

Finally figured out a solution to a problem I've been working on for a while... thought I would share the idea in case any of you might find it useful.

First the Problem:

We have a customer with about 200 client boxes (some via Citrix) who is running a bunch of custom programs. The custom programs (which I didn't right btw) mostly work now.

But once in a while.... (2 or 3 times a month) one of the custom programs fails to write information into the databases for the accounts payable system.

If this were easily repeatable we would simply run the program with DbgView running to catch the trace info until we found it. But DbgView (which reads the windows OutputDebugString channel) only works on one box at a time.

I guess we could run 200 copies of DbgView, one on each client, and then collect the data files daily or something. But this a management nightmare from the customers perspective. Blech!

Some Basic Assumptions:

Solution:

Benefits:

Once this is done it becomes a data analysis chore; but a manageable one.

Useful Links

RSyslog - a syslog alternative. There is a ton of installation and configuration information in the Documentation pages.

KLog - a free suite of syslog message sending tools for the Windows platform. This allows you to add syslog message sending capabilities to your applications or batch files. Tools include: Console, Win32-API, COM and .Net components.

phpLogCon - a web based syslog data interface

VMWare - home of the free VMWare player and other VM tools


Terry Bayne's Somewhat Transitional Web Site
http://www.tbayne.net/article.php?story=20070726171400966