Running a distributed application - on multiple servers, creates a need for logging to a central location, to help an admin monitor what the different parts are doing.

When we first encountered the problem in HiveSight we created twitter-log4j that lets you easily "log" messages to twitter from your java code. However, twitter has rate limits so you can't log as much as you want. It also lacks a good way to search the log.

This project, AppEngineLogger uses a Google App Engine application as the central logging repository. It receives log messages over http, stores them in its datastore, and displays messages to your users.

There's a sample application deployed on http://logservertest.appspot.com/ that you can play with. When you're ready, deploy your own on your google applications domain, so that only your org's users will be able to see the logs.