My team has to setup monitoring on transitioned servers using the Event Monitoring that comes with Domino. Simple tasks such as monitor deadmail levels and running tasks, and some replication checks.
We need to have the events dump into the NT Event Logs for an external monitoring system to pick it up. So far so good, and we got it going… but we’re not sure we understand how it works in the background.
I know the Event task picks up events generated by the domino server according to the criterias met in an Event Generator document, which then refers to its Event Handler to know what to do with it…
What I don’t get is… Let’s say the server has 200 deadmail, and you have a threshold set to 50. How does it know how often to trigger the alarm and which process does it exactly (the interval check)?
I know there’s a ServerCollection document in events4 in a view called “Statistics Collection”, which is set to report every 30 minutes, and alert every 15 minutes, but inside it says to log in statrep.nsf… so I’m confused. Does this mean that it will log every event that have an event generator in the statrep database every 30 minutes no matter what the event handler says for each and only actually trigger the action of the event handler (write in the NT event logs) every 15 minutes?
(1) For example, does this mean we’d be getting an alert for deadmail (monitoring team pages us when it finds a match in the event logs) every 15 minutes until we clear the deadmail?
(2) Another thing we’re wondering is how can we trigger the alarm manually to test it? Which task or command do we have to do to force it to run and bypass its interval delay (and write the entry in the event logs)? (providing we manually copy a bunch of deadmail that exceeds the threshold).
I’ve read through some documentation in the Admin help and the yellow-book too, but I need examples to put it all in context.
Thanks!