Creating Directory probes - Need a Domino Consultant? Call NotesMail +1 212-599-2048- HCLSoftware Business Partner

ADMINISTERING

Creating Directory probes
Create a directory probe as follows.

Procedure

1. From the Domino® Administrator, click the Files tab.

2. Open the Monitoring Configuration database (EVENTS4.NSF).

3. Expand DDM Configuration.

4. Choose any DDM probe view, and then click New DDM Probe.

5. Choose Directory.

Table 1. Probe subtype selection

Field	Action
Probe Subtype	Choose one: Directory Availability Directory Catalog Aggregation Schedule Directory Catalog Creation Directory Indexer Process State LDAP Process State LDAP Search Response LDAP TCP Port Health LDAP View Update Algorithm Name Lookup Search Response Secondary LDAP Search Response
Probe Description	Type a short description of the probe.
Severity	Choose the severity that will generate an event.
Which server(s) should run this probe?	Choose one: All servers in the domain -- Runs the probe on all servers in the domain. Special target servers -- Specify the type of servers to run the probe, such as POP3 servers or the administration server for the Domino Directory. Only the following servers -- Specify the servers on which the Directory probe will run.
Which server(s) should be probed?	Choose one: All servers in the domain -- Probes all servers in the domain. Only the following servers: -- Probes the servers that you specify.

Table 2. Probe subtype options

If you chose this probe subtype Enter this information

Directory Availability Enable or disable reporting on view-update issues and local LDAP directory serving issues. The probe always reports general directory availability issues.

Directory Catalog Aggregation Schedule Enable or disable generating events. If you enable the setting, enter the number of minutes after which missed aggregations are reported and enter the number of minutes after which long-running aggregations are reported.

Name Lookup Search Response Enable or disable generating an event when the Domino Directory search response exceeds the specified number of responses. For any settings that are enabled, enter the number of responses after which an event is generated. The severity of the event is shown in the column Generate an event of severity.

LDAP Search Response Enable or disable generating events. For any severities that are enabled, enter the average LDAP search response maximum value in milliseconds or as a percentage of the LDAP Server timeout. To use percentages, the LDAP Server timeout must be set to a value other than unlimited. Percentages override the millisecond threshold defined for a severity. If the probe encounters an average LDAP search response time that is greater than the value that you enter, an event is generated. The severity of the event is shown in the column Generate an event of severity.
You can also choose to limit monitoring to only the longest running searches stored in LDAP Server memory.

LDAP TCP Port Health Choose the services to which the probe applies, and then enter a time-out value. If the probe encounters a time-out greater than the value that you enter, an event is generated.

Secondary LDAP Search Response Enable or disable individual settings defining the maximum allowable secondary LDAP average search response time. If a secondary LDAP average search response time exceeds the value that you enter, and the setting is enabled, an event is generated. The severity of the event is shown in the columnGenerate an event of severity.

Table 3. Schedule options

Field Action

How often should this probe run? Choose one:

Run multiple times per day -- If you choose this option, complete the field Defined schedule.
Daily -- If you choose this option, complete the field On which days should this probe run .
Weekly -- If you choose this option, complete the field On which day of the week should this probe run.
Monthly -- If you choose this option, complete the field On which day of the month should this probe run.

Defined schedule Specify the number of minutes between each run of the probe.

Should this probe run twenty-four hours per day, seven days per week? Choose one:

Yes -- The probe runs continuously.
No --The probe runs according to a schedule that you define. After you choose this option, complete the field On which days should this probe run.

On which days should this probe run? Choose the days on which to run the probe.

On which day of the week should this probe run? Choose the day on which to run the probe.

On which day of the month should this probe run? Enter the day of the month on which to run this probe. For example, enter 15 to run the probe on the 15th day of the month.

During which hours of the day should this probe run? Specify the start time in the From field, and the end time in the To field. The probe will run during those hours.

At what time should this probe run? Choose the time at which you want the probe to run.

How should missed probes be handled? Choose one:

Ignore missed probe -- The missed probe is not run or rescheduled.
Run missed probe at startup -- The next time that the server starts, the missed probe runs.
Run missed probe at next time range -- The missed probe reschedules itself once. For example, if a probe scheduled to run every Tuesday at 5:00 AM fails to run, the probe reschedules itself to run on Wednesday at 5:00 AM. After that, the probe returns to its regular schedule.

Related concepts
Directory Probes
DDM probes

Help on Help

All Help Contents

Help on Help

All Help Contents

If you chose this probe subtype	Enter this information
Directory Availability	Enable or disable reporting on view-update issues and local LDAP directory serving issues. The probe always reports general directory availability issues.
Directory Catalog Aggregation Schedule	Enable or disable generating events. If you enable the setting, enter the number of minutes after which missed aggregations are reported and enter the number of minutes after which long-running aggregations are reported.
Name Lookup Search Response	Enable or disable generating an event when the Domino Directory search response exceeds the specified number of responses. For any settings that are enabled, enter the number of responses after which an event is generated. The severity of the event is shown in the column Generate an event of severity.
LDAP Search Response	Enable or disable generating events. For any severities that are enabled, enter the average LDAP search response maximum value in milliseconds or as a percentage of the LDAP Server timeout. To use percentages, the LDAP Server timeout must be set to a value other than unlimited. Percentages override the millisecond threshold defined for a severity. If the probe encounters an average LDAP search response time that is greater than the value that you enter, an event is generated. The severity of the event is shown in the column Generate an event of severity. You can also choose to limit monitoring to only the longest running searches stored in LDAP Server memory.
LDAP TCP Port Health	Choose the services to which the probe applies, and then enter a time-out value. If the probe encounters a time-out greater than the value that you enter, an event is generated.
Secondary LDAP Search Response	Enable or disable individual settings defining the maximum allowable secondary LDAP average search response time. If a secondary LDAP average search response time exceeds the value that you enter, and the setting is enabled, an event is generated. The severity of the event is shown in the columnGenerate an event of severity.

Field	Action
How often should this probe run?	Choose one: Run multiple times per day -- If you choose this option, complete the field Defined schedule. Daily -- If you choose this option, complete the field On which days should this probe run . Weekly -- If you choose this option, complete the field On which day of the week should this probe run. Monthly -- If you choose this option, complete the field On which day of the month should this probe run.
Defined schedule	Specify the number of minutes between each run of the probe.
Should this probe run twenty-four hours per day, seven days per week?	Choose one: Yes -- The probe runs continuously. No --The probe runs according to a schedule that you define. After you choose this option, complete the field On which days should this probe run.
On which days should this probe run?	Choose the days on which to run the probe.
On which day of the week should this probe run?	Choose the day on which to run the probe.
On which day of the month should this probe run?	Enter the day of the month on which to run this probe. For example, enter 15 to run the probe on the 15th day of the month.
During which hours of the day should this probe run?	Specify the start time in the From field, and the end time in the To field. The probe will run during those hours.
At what time should this probe run?	Choose the time at which you want the probe to run.
How should missed probes be handled?	Choose one: Ignore missed probe -- The missed probe is not run or rescheduled. Run missed probe at startup -- The next time that the server starts, the missed probe runs. Run missed probe at next time range -- The missed probe reschedules itself once. For example, if a probe scheduled to run every Tuesday at 5:00 AM fails to run, the probe reschedules itself to run on Wednesday at 5:00 AM. After that, the probe returns to its regular schedule.