Home
Administering
This documentation provides information about the administration tools for managing and monitoring servers and databases.
Monitoring servers
This section describes how to use the tools and features that help you monitor a Domino® system.
Server Health Monitor
You can monitor and troubleshoot performance issues using a number of different tools.
Using the Server Health Monitor
Using the Server Health Monitor, you can perform various tasks to monitor the health of servers and server components.
Selecting server components to include in health reports
Each server you monitor has a Health Monitoring Configuration document in the Health Monitoring database (DOMMON.NSF). This document specifies the server components you want to include in health reports.

Administering
This documentation provides information about the administration tools for managing and monitoring servers and databases.
- Administration tools
  Topics in this section describe the tools you can use to administer a Domino® server.
- Managing users
  The Administration Process helps you manage users by automating many of the associated administrative tasks. For example, if you rename a user, the Administration Process automates changing the name throughout databases in the Notes® domain by generating and carrying out a series of requests, which are posted in the Administration Requests database.
- Monitoring servers
  This section describes how to use the tools and features that help you monitor a Domino® system.
  - Monitoring the Domino® system
    You can monitor system activity and platform use using the Domino® Administrator or the server console.
  - Server Health Monitor
    You can monitor and troubleshoot performance issues using a number of different tools.
    - Server Health Monitor statistics
      The Server Health Monitor reports a statistic for the overall server and for individual components. Each statistic corresponds to a rating.
    - Server Health Monitor ratings
      The Current® Reports view of the Health Monitoring database (DOMMON.NSF) displays the assigned rating for each enabled server and server component. When a server rating is Warning or Critical, the Overall Health Report provides recommendations for correcting the problems.
    - Using the Server Health Monitor
      Using the Server Health Monitor, you can perform various tasks to monitor the health of servers and server components.
      - Selecting server components to include in health reports
        Each server you monitor has a Health Monitoring Configuration document in the Health Monitoring database (DOMMON.NSF). This document specifies the server components you want to include in health reports.
      - Setting up statistic alarms for the Server Health Monitor
        Just as you create an event generator for a Domino® system statistic, you create an event generator for a health statistic. Then when the statistic does not meet the defined threshold, an event is generated.
      - Modifying threshold values for the Server Health Monitor
        The Index Thresholds view in the Health Monitoring database (DOMMON.NSF) displays the threshold values for each platform. To modify the sensitivity to a particular component, change the threshold value. For example, if you want to run your networks with higher utilization for servers running on a specific platform, increase the threshold for the Network Utilization component for the platform.
    - Server Health reports
      Based on information gathered by the Domino® Server Monitor, the Server Health Monitor issues Health reports. Health reports are stored in the Health Monitoring database (DOMMON.NSF).
    - Working with Server Health Monitor statistics
      Health statistics are recorded in the Monitoring Results database (STATREP.NSF).
    - Viewing server health with the Server Health Monitor
      After the first polling interval passes, the Server Health Monitor posts a report of server health, which you can view in the Domino® server monitor for a quick visual representation of your server's health.
  - Entitlement tracking
    As of Domino 12.0, a new internal mechanism is provided for collecting the highest entitlement that individual users have across a Domino domain. When a user appears in the ACL of a database with Reader access or above and that person has the right to access the server, the user is said to be an entitled user.
  - Domino® domain monitoring (DDM)
    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.
  - The Domino® SNMP Agent
    The Domino® SNMP Agent enhances the monitoring and control features of Domino by enabling third-party management stations, which use industry standard SNMP, to manage aspects of the Domino server.
  - Overview of server maintenance
    As a Domino® administrator, a major part of your job is maintaining each server that you administer.
  - Tools for mail monitoring
    Domino® provides three tools that you can use to monitor mail. Message tracking allows you to track specific mail messages to determine if the intended recipients received them. Mail usage reports provide the information you need to resolve mail problems and improve the efficiency of your mail network. Mail probes test and gather statistics on mail routes.
  - Monitoring directory assistance
    You can monitor directory assistance by using Show Xdir command to display information about all the directories a server uses for directory services. You can also view directory assistance statistics.
  - Monitoring databases
    You can monitor database activity, replication, and document deletions.
  - Monitoring a cluster
    Domino® provides several ways to find out what is happening in a cluster and make adjustments to keep the cluster running smoothly and efficiently, so that no server is overloaded. You can monitor failover, workload balancing, and cluster replication to see how efficiently the cluster is running.
  - Monitoring slow or unresponsive servers with the Domino® Diagnostic Probe
    Use the Domino® Diagnostic Probe (DDP), a Java™ utility provided by Support, to monitor servers that have been intermittently slow or unresponsive. The probe is a Java process (dbopen.jar) that runs in the background. The utility probes a specific Domino server over time by invoking database open transactions. If the probe detects a slow response, it will invoke Notes® System Diagnostic (NSD) to gather diagnostic data. This data is used by Support to troubleshoot and determine the cause or causes of the performance degradation.
  - Monitoring quality of service
    Quality of Service, or QoS, is designed to react to the general operation of a Domino® server in order to keep that server functioning reliably and always available. If QoS detects that a server is not responding or hung, QoS probing can be configured to email an administrator about the problem and/or automatically terminate the server and restart it. QoS log information can also be useful for analysis by Support.
  - Understanding Quality of Service (QoS) behavior and logging
    This topic covers details of QoS including server and server controller behavior during kill events, failover trigger, and log file content.
- Managing servers
  Manage Domino® servers by performing any of these tasks.
- Managing databases
  Topics in this section describe how to set up and manage Domino® databases.

Selecting server components to include in health reports

Each server you monitor has a Health Monitoring Configuration document in the Health Monitoring database (DOMMON.NSF). This document specifies the server components you want to include in health reports.

About this task

Based on statistics and task information obtained from the server, the Server Health Monitor automatically determines which components to include in health reports. For example, if the HTTP task is not running on a particular server, then the Server Health Monitor automatically excludes the HTTP component from any analysis.

Occasionally, you may want to exclude a component manually. For example, if you know that a particular server has a disk I/O bottleneck, exclude the Disk Utilization component so that it doesn't adversely affect the server's overall health rating.

Server components that are selecting components manually display a pencil icon next to the server name. If there is no pencil icon, the components are being selected automatically.

To select server components to include

Procedure

From the Domino® Administrator, click the Server > Monitoring tab.
From the menu, select Monitoring > Switch to Health Reports, and then open the Configuration view.
Select Server Components.
Select the server you want to modify, and click Edit Server Document.
Under How should component indices be enabled? choose one:
- Automatic -- to allow the Server Health Monitor to select the components to include in health reports, based on which server tasks are running.
- Custom -- to manually select the components to include in health reports. Statistics for selected components are included in health reports, whether the server task is running or not.

To reset server component select to automatic

Procedure

From the Domino® Administrator, click the Server > Monitoringtab.
From the menu, select Monitoring > Switch to Health Reports, and then open the Configuration view.
Select Server Components.
Select the server you want to modify, and click Edit Server Document.
Click Restore Automatic Selections and click OK.