122 Chapter 7. Monitoring
If config management is enabled on the systems to be monitored, you may deploy this file
across systems using a config channel. Refer to Section 6.6.6.1 Preparing Systems for Config
Management for details.
Note
If valid entries already exist in authorized_keys, add the daemon key to the file rather than
use it to replace it.Do this by saving the copied text to id_dsa.pub in the same .ssh/ directory
and then running the command: cat ~/.ssh/id_dsa.pub >> ~/.ssh/authorized_keys.
5. Finally, ensure the .ssh/ directory and authorized_keys file have the appropriate permis-
sions set. This can be done as the daemon’s user with the following commands:
chmod 700 ~/.ssh
chmod 600 ~/.ssh/authorized_keys
Once the key is in place and accessible, all probes that require it should begin to allow ssh connec-
tions between the Monitoring infrastructure and the monitored system. You may then schedule probes
requiring the monitoring daemon to run against the newly configured systems.
7.3. Notifications
In addition to viewing probe status within the RHN interface, you may be notified whenever a probe
changes state. This is especially important when monitoring mission-critical production systems. For
this reason, Red Hat recommends taking advantage of this feature.
To enable probe notifications within RHN, you must have identified a mail exchange server and mail
domain during installation of your RHN Satellite Server and configured sendmail to properly handle
incoming mail. Refer to the Installation chapter of the RHN Satellite Server Installation Guide for
details.
7.3.1. Creating Notification Methods
Notifications are sent to a notification method, in essence an email or pager address associated with
a specific RHN user. Although the address is tied to a particular user account, it may serve multiple
administrators through an alias or mailing list. Andeach user account can contain multiple notification
methods. To create a notification method:
1. Log into the RHNwebsite as either anOrganization Administrator or Monitoring Administrator.
2. Navigate to the User Details
Notification Methods tab and click create new method.
3. Enter an intuitive, descriptive label for the method name, such as DBA day email, provide
the correct email or pager address. Remember, the labels for all notification methods will be
available in a single list during probe creation, so they should be unique to your organization.
4. Select the checkbox if you desire abbreviated messages to be sent to the pager. This shorter
format contains only the probe state, system hostname, probe name, time of message, and Send
ID. The standard, longer format displays additional message headers, system and probe details,
and instructions for response.
5. When finished, click Create Method. The new method shows up in the User Details
Noti-
fication Methods tab and the Notification page under the top Monitoring category. Click its
name to edit or delete it.
