A Good Looking Event Log

I’ve been using Event Logging extensively to monitor various processes and background tasks in my Community Server-based Jobs Management Application.  This morning’s report is a great example of using the Event Log with custom application events.

Starting with #1 at the bottom of the screen pic we see that our Keep Alive program to support after-hour background tasks runs every 15 minutes as scheduled, which means that the 11:00 PM task that transfers the day’s Truck charges to an external Inventory Management system executes and completes successfully (2).  The website shuts down after the Keep Alive program completes its run and starts back up at 6:35 AM (3).  Around 7:25 AM a foreman closes a job in the field, so a background task that transfers all of that job’s charges to billing found a job flagged for transfer and performed successfully (4).  Finally (5), the built-in email task successfully notified the billing group that the job was closed.

 

Article written by

A long time developer, I was an early adopter of Linux in the mid-90's for a few years until I entered corporate environments and worked with Microsoft technologies like ASP, then .NET. In 2008 I released Sueetie, an Online Community Platform built in .NET. In late 2012 I returned to my Linux roots and locked in on Java development. Much of my work is available on GitHub.