Viewing events in the Domino® Domain Monitor database

Use the Domino® Domain Monitor database (DDM.NSF) to view events sorted by severity, type, server, date or assignment. You can also view open events, recent events or all events simply by clicking a tab in these views.

Use the My Events view to view only those events that are assigned to you. When you open the Domino® Domain Monitor database, data is presented at a high level, but you can choose to view detailed information about a particular event or set of events. You can also toggle between viewing unread events or all events. If you notice that a particular event is generated frequently, you can view a detailed history of that event to assist you in determining a cause and solution for the event.

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. The message 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. The first time that an event is logged to the Domino® Domain Monitor database, one of these states is automatically assigned to the event:

• Open -- The event has a non-normal severity and the administrator has not closed the event.
• Closed -- The event has a normal severity or an administrator has closed the event. If a Closed event is later reported with non-normal severity, the event state changes to Open.
• Permanently Closed -- An administrator has marked the event Permanently Closed. These events never reopen automatically, but an administrator can reopen them or designate them as Closed.

Every time that a probe runs, event documents are updated. If the severity of an event changes, the event's state automatically changes accordingly. The event state is determined by the event severity. Events with a severity of normal are closed; events with a severity of non-normal are open. An event's state can automatically change many times between Open and Closed. Permanently Closed events are never automatically opened or pended. When you assign an event state of Permanently Closed to an event, that state is maintained as a fixed state unless you manually change the state back to Open or Closed. Permanently Closed is a stable category for resolved problems, obsolete problems, or problems that you simply want to ignore.

After you review or assign an event, you can manually assign it a state of Open, Closed, or Permanently Closed.

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.

You can look at the Event Change History section of the Event documents to see previous event change activity.