Chapter 7. Monitoring 1735. On the System Details ⇒ Probes tab, select another notification method and clickUpdate Probe.6. You may now return to the Monitoring ⇒ Notifications page and delete the notifi-cation method.7.5. ProbesNow that the Red Hat Network Monitoring Daemon has been installed and notificationmethods have been created, you may begin installing probes on your Monitoring-entitledsystems. If a system is entitled to Monitoring, a Probes tab appears within its SystemDetails page. This is where you will conduct most probe-related work.7.5.1. Managing ProbesTo add a probe to a system, the system must be entitled to Monitoring. Further, you musthave access to the system itself, either as the system’s root user, through the System GroupAdministrator role, or as the Organization Administrator. Then:1. Log into the RHN website as either an Organization Administrator or the SystemGroup 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 theProbe Command Group. This alters the list of available probes and other fields andrequirements. Refer to Appendix C Probes for the complete list of probes by com-mand group. Remember that some probes require the Red Hat Network MonitoringDaemon to be installed on the client system.4. Select the desired Probe Command and the Monitoring Scout, typically RHNMonitoring Satellite but possibly an RHN Proxy Server. Enter a brief butunique description for the probe.5. Select the Probe Notifications checkbox to receive notifications when the probechanges state. Use the Probe Check Interval pulldown menu to determine howoften notifications should be sent. Selecting 1 minute (and the Probe Notificationcheckbox) means you will receive notifications every minute the probe surpasses itsCRITICAL or WARNING thresholds. Refer to Section 7.4 Notifications to find outhow to create notification methods and acknowledge their messages.6. Use the RHNMD User and RHNMD Port fields, if they appear, to force the probeto communicate via sshd, rather than the Red Hat Network Monitoring Daemon.Refer to Section 7.2.3 Configuring SSH for details. Otherwise, accept the default val-ues of nocpulse and 4545, respectively.
