Lotus Domino Administrator 8.5 Help - Creating Database probes

MONITORING

Creating Database probes
1. From the IBM® Lotus® Domino® Administrator, click the Files tab.

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

3. Choose DDM Configuration.

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

5. Choose Database.

6. Complete these fields on the Basics tab. The actual fields and tabs that are available to be completed depends on the probe that you choose.

Field Action

Probe Subtype Choose one:

Error Monitoring
Scheduled Checks

Probe Description Enter a short description of the probe.

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 Database probe will run.

Severity Choose the severity level that generates an event.

Select one or more databases to probe Select the names of databases to probe.

Monitor database for unused space Click the check box to designate that the probe should monitor the specified database for unused space.

Monitor database for user inactivity Click the check box to designate that the probe should monitor user activity for the specified database.

What periods do you want to monitor and what are the minimum number of sessions that must be met before generating an event? Do both of these:

Choose the time periods to monitor -- daily, weekly, or monthly.
For each time period that you chose, in the Minimum Sessions field, enter the number of minimum sessions after which an event will be generated.

Errors to ignore This field lists the errors that are ignored and therefore do not generate an event.
Choose one or both:

Add Error Codes to the List -- Select error codes to add, and then click OK.
Remove Error Codes from List -- Select error codes to remove, and then click OK.

7. If you are creating a Database -- Scheduled Checks probe, complete these fields on the Schedule tab. (For all other probes, continue with Step 8.)

Field Action

How often should this probe run? Choose one:

Run multiple times per day -- The probe runs more than once each day. Causes the "Defined schedule" field to display.
Daily -- The probe runs once each day. Use the field "On which days should this probe run" to specify the days on which the probe is run.
Weekly -- The probe runs once each week. Use the field "On which day of the week should this probe run?" to specify the day on which the probe is run.
Monthly -- The probe runs once each month. Use the "On which day of the month should this probe run" field to specify when the probe should run.

Defined schedule Specify the number of minutes that should pass 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.

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

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

During which hours of the day should this probe run? Specify the probe starting time in the From field, and the probe ending time in the To field.

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

At what time should this probe run? Choose the time to run the probe.

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.

8. Click Save and Close.

Related topics

DDM probes

Glossary

Feedback on Help or Product Usability?

Help on Help

All Help Contents

Glossary

Field	Action
Probe Subtype	Choose one: Error Monitoring Scheduled Checks
Probe Description	Enter a short description of the probe.
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 Database probe will run.
Severity	Choose the severity level that generates an event.
Select one or more databases to probe	Select the names of databases to probe.
Monitor database for unused space	Click the check box to designate that the probe should monitor the specified database for unused space.
Monitor database for user inactivity	Click the check box to designate that the probe should monitor user activity for the specified database.
What periods do you want to monitor and what are the minimum number of sessions that must be met before generating an event?	Do both of these: Choose the time periods to monitor -- daily, weekly, or monthly. For each time period that you chose, in the Minimum Sessions field, enter the number of minimum sessions after which an event will be generated.
Errors to ignore	This field lists the errors that are ignored and therefore do not generate an event. Choose one or both: Add Error Codes to the List -- Select error codes to add, and then click OK. Remove Error Codes from List -- Select error codes to remove, and then click OK.

Field	Action
How often should this probe run?	Choose one: Run multiple times per day -- The probe runs more than once each day. Causes the "Defined schedule" field to display. Daily -- The probe runs once each day. Use the field "On which days should this probe run" to specify the days on which the probe is run. Weekly -- The probe runs once each week. Use the field "On which day of the week should this probe run?" to specify the day on which the probe is run. Monthly -- The probe runs once each month. Use the "On which day of the month should this probe run" field to specify when the probe should run.
Defined schedule	Specify the number of minutes that should pass 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.
On which days should this probe run?	Choose the days on which the probe runs.
On which day of the week should this probe run?	Choose the day on which the probe runs.
During which hours of the day should this probe run?	Specify the probe starting time in the From field, and the probe ending time in the To field.
On which day of the month should this probe run?	Enter the day of the month on which to run the probe. For example, enter 15 to run the probe on the 15th day of each month.
At what time should this probe run?	Choose the time to run the probe.
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.