Installation guide

Note

Since both the notification method name and address can be edited, consider updating the

method rather than deleting it. T his redirects notifications from all probes using the method

without having to edit each probe and create a new notification method.

4. If the method is associated with one or more probes, you are presented with a list of the probes

using the method and the systems to which the probes are attached instead of a confirmation

page. Click the probe name to go directly to the System Details → Probes tab.

5. Select another notification method and click Update Probe.

6. Return to the Monit oring → Not ifications page and delete the notification method.

1.2.5. About Probes

Now that the Red Hat Network monitoring daemon has been installed and notification methods have

been created, you may begin installing probes on your monitoring-entitled systems. If a system is entitled

to monitoring, a Probes tab appears within its System Details page. T his is where you will conduct

most probe-related work.

1.2.5.1. Managing Probes

Probes are created through the Red Hat Satellite server. Once the probe has been created, the probes

are propagated to the specified monitoring-entitled systems registered to the Satellite. Follow the steps

below to add a probe in the Satellite server:

1. Log into the Satellite as either a Satellite Administrator or the System Group Administrator for the

system.

2. Navigate to the System Details → Probes tab and click create new probe.

3. On the System Probe Creation page, complete all required fields. First, select the Probe

Command Group. This alters the list of available probes and other fields and requirements. See

Appendix A, Probes for the complete list of probes by command group. Remember that some

probes require the Red Hat Network monitoring daemon to be installed on the client system.

4. Select the desired Probe Command and the monitoring Scout, typically Red Hat Monitoring

Satellite but possibly a Red Hat Satellite Proxy Server. Enter a brief but unique description for

the probe.

5. Select the Probe Notifications checkbox to receive notifications when the probe changes

state. Use the Probe Check Interval dropdown menu to determine how often notifications

should be sent. Selecting 1 minute (and the Probe Notification checkbox) means you will

receive notifications every minute the probe surpasses its CRITICAL or WARNING thresholds.

See Section 1.2.4, “Enabling Notifications” to find out how to create notification methods and

acknowledge their messages.

6. Use the RHNMD User and RHNMD Port fields, if they appear, to force the probe to communicate

via sshd, rather than the Red Hat Network monitoring daemon. See Section 1.2.2.2, “Configuring

SSH” for details. Otherwise, accept the default values of nocpulse and 4 545, respectively.

7. If the T imeout field appears, review the default value and adjust to meet your needs. Most but

not all timeouts result in an UNKNOWN state. If the probe's metrics are time-based, ensure the

timeout is not less than the time allotted to thresholds. Otherwise, the metrics serve no purpose,

as the probe will time out before any thresholds are crossed.

8. Use the remaining fields to establish the probe's alert thresholds, if applicable. These CRITICAL

and WARNING values determine at what point the probe has changed state. See Section 1.2.5.2,

Chapter 1. Red Hat Satellite Information