Subject: Agent Logging
There can be advantages to logging all agents into a central db. There is a problemif you go across servers since background agents can’t connect to another server unless
you configure the servers to be trusted (only available in R6).
I also trace agents running in a database by logging their run in a document.
I have found these traces great for determining production problems. However, I
also got tired of watching all the traces each day. So I created a central
event monitoring application. This application is a central catcher for
“events of significance” for all agents (regardless of where they run).
See the snip below from a previous post on this which was in reference to
determining server availability.
Just some food for thought.
HTH,
<<>>>>>>>>>>>>
I would suggest setting up your own Application Event Monitor (AEM) (see my article
reference below which has a free download database with sample code).
You would write an agent that tests the server(s) availability.
This agent would send an “Event Message” to the monitor confirming that everything is fine.
You’ll then configure an “Event Handler” that looks for a specific confirmation message
on a specific schedule (e.g. “Servers are alive and well” every 1 hour).
If this message is not received your “Event Handler” will send email to those concerned.
Event Handlers are setup for each application that you want to monitor and are highly
configurable. You specify the action to take when events are found and when they are NOT found.
Applications that do not report a status was my biggest interest in developing this tool.
I am working on a event action for a pager but it’s not available yet. Suggestions on how to
call a pager from LotusScript are welcome.
There is also a self monitoring feature with the tool so that I get notified each day
that the monitor itself is running ok. This tool has saved me countless
hours baby sitting applications. I only have to look for the monitor confirmation email
each morning and I don’t have to worry about all the other applications that I’ve
instrumented for monitoring.
Any application that can send e-mail or make a URL connection can be monitored.
I currently monitor stand-alone Java applications and DB2 scripts in addition to a
dozen or so Notes applications. I’ve also instrumented all my “On Error”
catchers so that they send messages to the monitor.
“AEM — A Tool for Automatically Monitoring Your Applications”
from THE VIEW, May/June 2004
http://www.eview.com/eview/viewr5.nsf/0/d5e78ab6f111a37f85256e9f004440d7?OpenDocument
HTH,
<<>>>>>>>>>>>>