Monday, 25 June 2018
Domino Domain Monitoring
In my recent role as Domino Administrator I picked up a number of tasks including monitoring our Domino Servers. Last week I watched episode 5 of the great #Perfect10 webcast by Gabriella Davis. In this webcast Gabriella mentioned the use of the Domino Domain Monitoring which is shipped with the Administrator Client. Below some basic information ans some links to useful resources for setting up the Domino Domain Monitoring. During the past few days I have set up the Domino Domain Monitoring further and this works correctly. The Domino Domain Monitoring database provides important information about our servers, the identified problems and possible solution. For every administrator a must to use together with the Domino Configuration Tuner (more information about the Domino Configuration Tuner in my previous blog post Using the Domino Configuration Tuner to Evaluate Server Settings). Domino Domain Monitoring (DDM) provides one location in the Domino Administrator client that can be used 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.
The UI for DDM is made up of two databases, events4.nsf and ddm.nsf.
The Monitoring Configuration (events4.nsf) database is used for configuring probes and DDM Filters and contains all events and formulas for how corrective actions are completed.
The Domino Domain Monitoring (ddm.nsf) database is the database where the results of probes are reported. They can be viewed in several different ways such as by severity, date, etc. This database is also where events can be assigned to administrators.
From the Domino Domain Monitor database administrators can select an event and view detailed information about an event. The administrators can use the Probable cause and possible solution tab to view information about the cause of the event, and, in some cases, use a database link to access the appropriate database from which the administrator can resolve the event. Some DDM Event documents include a Details tab that displays additional details about the event and a Correlation tab that contains links to other DDM Event documents that may be related to the open DDM Event document.
The first time that a Domino server starts, the Domino Domain Monitor database (DDM.NSF) is created from the DDM.NTF template.
Probes are the backbone of Domino domain monitoring and require Domino because they are embedded into the new server and addin task code. Probes are set and stored in individual Probe configuration documents, which are stored in the Monitoring Configuration database (events4.nsf). Probe configuration documents contain Basics, Target, and Specifics sections in the Basics tab. Depending on the probe type there may also be a Schedule tab in the document. All probes are categorized by a probe type. For each probe type, there are one or more probe subtypes. The probe subtypes further categorize the function of the probe.
Finally filters control the volume of Events that appear in DDM.nsf. Filters are used to specify what type of Events should be included in the Domino domain monitor database, not what Events should be excluded.
For more information:
Lotus Education on Demand: Domino Domain Monitoring (DDM)
RedBook Lotus Domino Domain Monitoring
Video Domino Configuration Tuner and Domino Domain Monitoring
Geplaatst door Johnny Oldenburger op Monday, June 25, 2018