Overview
IBM Lotus Domino domain monitoring (DDM) provides one location in the Domino Administrator client that you can use to view the overall status of multiple servers across one or more domains, and then use the information provided by DDM to quickly resolve problems. DDM requires a Domino 7 or more recent server.
DDM does the following:
- Automates problem determination and determines probable cause in multiple feature areas.
- Provides an active monitoring capability utilizing more than 50 new probes with highly-configurable schedules, content and targets.
- Provides a top-down, feature-oriented view of the domain status with the ability to selectively view detailed information on that status.
- Provides visual indicators for displaying which problems are most critical, which are resolved, and which are not.
- Provides default settings for probe configuration to make setup easy.
- Recognizes and reports critical server and client issues within minutes.
- Provides corrective actions and links to databases in order to resolve reported problems.
DDM uses configurable probes to gather information across multiple servers and then consolidates and reports that information on specially-designated collection servers in the Domino Domain Monitor database (DDM.NSF). A probe is a discrete check, or set of checks, configured to run against one or more servers, databases, and services. The probe returns status and server health information to DDM.NSF. Probes run according to a default schedule, a schedule that you specify, or on an as-needed basis as determined by the probe and the events on the server.
To gather and report information across multiple servers and domains, DDM uses a collection hierarchy consisting of servers that collect information from other servers, and node servers from which the information is collected. All event information is stored and consolidated in the Domino Domain Monitor that you can view. You specify the collection hierarchy, that is, which servers are collection servers and which are node servers. A collection hierarchy can be multi-tiered with collection servers collecting from other collection servers, but that is not required for DDM to run. As with the DDM probes, the collection hierarchy is easy to create and modify in a configuration user interface in the Monitoring Configuration database (EVENTS4.NSF).
New in DDM for Domino 8.0
- Any Domino event can be forwarded to Tivoli Enterprise Console (TEC) using a Domino Event Handler. In events4.nsf, under Event Handlers, create a New Event Handler. Under the action tab of the New Event Handler document, select "Forward event to Tivoli Enterprise Console". Some install kits inadvertently excluded the DOMINOSRV.baroc file, which is used by TEC to recognize the incoming Domino events. It is available for download here.
- Enhancement to the Directory Probe / LDAP Search Response probe -- Monitors the server's average search response time for LDAP searches. You may choose to monitor all searches executed on the server or limit monitoring to only the longest running searches stored in LDAP Server memory. Choosing the longest running searches option provides additional details on searches so they can be identified and addressed.
- Administration / Automatic Report Closing probe -- Use the Automatic Report Closing probe to close Event reports that have been open for a specified amount of time, but that are inactive during that time.
- Common Actions button on DDM.NSF Events document -- You can use the Common Actions button to access a list of the most commonly performed actions for resolving events, and then choose an action.
- Open the Domino Domain Monitoring database (DDM.NSF) when the Domino Administrator is started -- You can set an administration preference to open the Domino Domain Monitoring database (DDM.NSF) when the Domino Administrator client starts.
- New Execute CA role required to access Corrective Actions text and link -- To access the Corrective Action text and the link associated with a Corrective Action, you must be assigned the Execute CA role in the ACL for DDM.NSF.
- New Modular documents -- Modular documents are the reference documents for the Probable Cause, Possible Solution, and Corrective Actions statements. Every Probable Cause, Possible Solution, and Corrective Action statement has a corresponding and reusable Modular document.
Check out the Lotus Domino and Notes Information Center for more details about
DDM new features.
DDM vs. DCT
You will find a explanation of the differences between DDM and the Domino Configuration Tuner in the
DCT post in this wiki.
Resources
Domino Domain Monitoring 8.0 documentation
IBM Lotus Domino Information Center
Domino Domain Monitoring (DDM) educational resources
Self-guided slide show, demo movie, RedPaper, Lotus Education workshop documentation.
Related Topics
Domino Configuration Tuner
Evaluate Server Configuration
Activity Logging and Activity Trends
Load Balance Domino Servers