Listing 10 Example monitor.conf

# Example monitor.conf

#===========
# PARAMETERS
#===========

# The following parameters may be included in a configuration block:
#
# message_types
#     Valid values are "alert" and/or "summary". Determines whether
#     the block applies to the send_alerts or send_summary programs.
#     Defaults to the empty string, in which case the block will be ignored.
#     
#
# days_old
#     Integer representing a number of days. Max number of days old
#     that a sent alert can be. Only applies to send_summary.
#     Defaults to 1.
#
# priorities
#     List of priorities. An alert's priority must match one of
#     these priorities. Defaults to "high medium low info".
#
# include_classes
#     List of class names. An alert's class must match one of these
#     classes if the value of the parameter is not the empty string.
#     Defaults to the empty string.
#
# exclude_classes
#     List of class names. An alert will be excluded if its class 
#     matches one of the classes in the list. Defaults to the empty
#     string.
#
# address_type
#     Valid values are "email" or "pager". If address_type is "pager"
#     then only the header portion of the alert file will be sent;
#     otherwise, the entire alert will be sent. Defaults to "email".
#
# addresses
#     A list of addresses separated by white space. Used with mailx
#     to send alerts. Defaults to the empty string.
#
# addresses_files
#     A list of filenames separated by white space. Each file should
#     contain one address per line. Defaults to the empty string.
#
# users
#     A list of user names separated by white space. User names will
#     be mapped to addresses if an appropriate mapping function has
#     been implemented.
#
# users_files
#     A list of filenames separated by white space. Each file should
#     contain one username per line. Defaults to the empty string.
#
# clients
#     A list of host names. Alerts will be sent only if the host on
#     which they were generated is included in the list. Defaults to
#     the local host name.
#
# clients_files
#     A list of filenames separated by white space. Each file should
#     contain one host name per line.
#
# servers
#     A list of host names. Alerts will be sent only if the local host
#     is included in the list. This is useful when creating a single
#     configuration file that will be used on multiple hosts. Defaults
#     to the local host name.
#
# servers_files
#     A list of filenames separated by white space. Each file should
#     contain one host name per line.
#
# sudoers_users
#     A list of user aliases separated by white space and specified in
#     /etc/sudoers. Aliases will be mapped to user names, and user
#     names will be mapped to addresses if an appropriate mapping 
#     function has been implemented.
#
# sudoers_clients
#     A list of host aliases separated by white space and specified in
#     /etc/sudoers. Aliases will be mapped to host names.
#
# sudoers_servers
#     A list of host aliases separated by white space and specified in
#     /etc/sudoers. Aliases will be mapped to host names.
#
# days
#     A list of weekday names or three-letter abbreviations. If the list
#     is not empty, then alerts will only be sent if the current day
#     matches one of the days in the list. Defaults to the empty string.
#     
# begin_hour
#     An integer. If not null, then alerts will only be sent if the
#     current hour is greater than or equal to begin_hour. Defaults to
#     null.
#
# end_hour
#     An integer. If not null, then alerts will only be sent if the
#     current hour is less than or equal to end_hour. Defaults to null.
#
# timezone
#     A timezone name. Determins what timezone should be used when
#     calculating the current day and time. Defaults to the local
#     timezone.

#=========
# EXAMPLES
#=========

#-------------------------------------------------------------------
# Example 1:
#
# Note how comments can begin in the middle of a line.
#
addresses: john.doe@company.com # A very simple config block.

# Remember: Configuration block are separated by blank lines.

#-------------------------------------------------------------------
# Example 2:
#
# Note how comments can be interleaved within a block.
# Don't insert a blank line inadvertantly!
#
# message_types is specified explicity.
#
message_types: alert
#
# Three files contain the addresses that alerts will be sent to.
# Parameters that accept a list of values can appear multiple times,
# in which case values are concatenated to form a single list.
#
addresses_files: /opt/monitor/etc/addresses
addresses_files: /etc/addresses.1 /etc/addresses.2
#
# Only high and medium priority alerts will be sent.
#
priorities: high medium
#
# Alerts belonging to the classes "testing" and "test" are ignored.
#
exclude_classes: testing test

#-------------------------------------------------------------------
# Example 3:
#
# This block applies to individual alerts as well as summary reports.
#
message_types: alert summary
#
# Only alerts that are less than or equal to 5 days old will be 
# summarized.
#
days_old 5
#
# A variety of techniques can be used in combination with each other
# to specify the address list.
#
addresses: john.doe@company.com
address_files: /etc/addresses.1
users: bill betty bob beatrice
users_files: /etc/users.1 /etc/users.2
sudoers_users: administrators
#
# Only alerts belonging to the classes "testing" and "test" will be
# sent to the specified addresses.
#
include_classes: testing test
#
# Only alerts generated on the host "toy" will be sent.
#
clients: toy
#
# Alerts will only be sent from "toy".
#
servers: toy
#
# Alerts will only be sent Monday through Friday, after 1 PM.
#
days: mon Tuesday WED Thurs FRIDAY
begin_hour: 13
# End Listing 10.