MONITORING
Note Recent events consist of all Open events and all Closed events that had a status of Open during the previous 7 days.
Event messages often, include two statements -- a problem statement followed by a reason statement. For example,:
Unable to replicate with server server name: Server not responding.
The problem statement is the first statement and the reason statement is the second statement. (In this example, the two statements are separated by a colon, but messages comprised of one statement can also have colons.) Each statement has its own type and severity. "Unable to replicate with server server name" has the message type and the severity of Replication/Failure, and "Server not responding" has the message type and severity of Resource/Failure. Messages that are comprised of two statements generate two events. There is no definitive way to determine whether a message is comprised of one statement or of two, but when a message statement follows the pattern of problem statement followed by a reason statement, two events are usually generated.
To view an event message that was generated by a pre-IBM® Lotus® Domino® 7 event generator, open the Monitoring Configuration database (EVENTS4.NSF), and then open the view Advanced -- Message by Text to view how that event message is categorized in DDM. The information on the Basics panel shows the name of the new Event Type and the Old Event Type. In DDM, there are 10 event types and in pre-Domino 7, there are 22 event types. You use the information on the Basics panel to see how the old event types are incorporated into the new event types. For example, this event message has Server as the Event Type and Mail as the Old Event Type
Compacting <database name>
The first time that an event is logged to the Domino Domain Monitor database, one of these states is automatically assigned to the event:
After you review or assign an event, you can manually assign it a state of Open, Closed, or Permanently Closed.
Note To change an event's state, you must have a minimum of Author access with the role Change State in the ACL for DDM.NSF. The Change State button does not display if you do not have the required access.
The Document Change History section of the Event documents records details about assignment and state changes so that you can determine what has changed, when the change occurred, and who initiated the change.
Note To assign or reassign an event to an administrator, you must have a minimum of Author access with the role Assign Events in the ACL for DDM.NSF. If you lack the required access, the Assign Events and Reassign Events buttons do not display.
You can look at the Event Change History section of the Event documents to see previous event change activity.
Related topics