Теми рефератів
> Реферати > Курсові роботи > Звіти з практики > Курсові проекти > Питання та відповіді > Ессе > Доклади > Учбові матеріали > Контрольні роботи > Методички > Лекції > Твори > Підручники > Статті Контакти
Реферати, твори, дипломи, практика » Статьи » Система моніторингу ресурсів та сервісів локальної обчислювальної мережі

Реферат Система моніторингу ресурсів та сервісів локальної обчислювальної мережі





this host templategeneric-host; Inherit default values ??from the generic-host template_period 24x7; By default, printers are monitored round the clock_interval 5; Actively check the printer every 5 minutes_interval 1; Schedule host check retries at 1 minute intervals_check_attempts 10; Check each printer 10 times (max) _command check-host-alive; Default command to check if printers are alive _period workhours; Printers are only used during the workday_interval 30; Resend notifications every 30 minutes_options d, r; Only send notifications for specific host states_groups admins; Notifications get sent to the admins by default0; DONT REGISTER THIS - ITS JUST A TEMPLATE

}


# Define a template for switches that we can reusehost {generic-switch; The name of this host templategeneric-host; Inherit default values ??from the generic-host template_period 24x7; By default, switches are monitored round the clock_interval 5; Switches are checked every 5 minutes_interval 1; Schedule host check retries at 1 minute intervals_check_attempts 10; Check each switch 10 times (max) _command check-host-alive; Default command to check if routers are alive _period 24x7; Send notifications at any time_interval 30; Resend notifications every 30 minutes_options d, r; Only send notifications for specific host states_groups admins; Notifications get sent to the admins by default0; DONT REGISTER THIS - ITS JUST A TEMPLATE

}


# SERVICE TEMPLATES

# Generic service definition template - This is NOT a real service, just a template!

service {generic-service; The name of this service template_checks_enabled 1; Active service checks are enabled_checks_enabled 1; Passive service checks are enabled/accepted_check 1; Active service checks should be parallelized (disabling this can lead to major performance problems) _over_service 1; We should obsess over this service (if necessary) _freshness 0; Default is to NOT check service freshness _enabled 1; Service notifications are enabled_handler_enabled 1; Service event handler is enabled_detection_enabled 1; Flap detection is enabled_prediction_enabled 1; Failure prediction is enabled_perf_data 1; Process performance data_status_information 1; Retain status information across program restarts_nonstatus_information 1; Retain non-status information across program restarts_volatile 0; The service is not volatile_period 24x7; The service can be checked at any time of the day_check_attempts 3; Re-check the service up to 3 times in order to determine its final (hard) state_check_interval 10; Check the service every 10 minutes under normal conditions_check_interval 2; Re-check the service every two minutes until a hard state can be determined_groups admins; Notifications get sent out to everyone in the admins group_options w, u, c, r; Send notifications about warning, unknown, critical, and recovery events_interval 60; Re-notify about service problems every hour_period 24x7; Notifications can be sent out at any time0; DONT REGISTER THIS DEFINITION - ITS NOT A REAL SERVICE, JUST A TEMPLATE!

}


# Local service definition template - This is NOT a real service, just a template!

service {local-service; The name of this service templategeneric-service; Inherit default values ??from the generic-service definition_check_attempts 4; Re-check the service up to 4 times in order to determine its final (hard) state_check_interval 5; Check the service every 5 minutes under normal conditions_check_interval 1; Re-check the service every minute until a hard state can be determined0; DONT REGISTER THIS DEFINITION - ITS NOT A REAL SERVICE, JUST A TEMPLATE!

}


/etc/nagios3/objects/timeperiods.cfg


# This defines a timeperiod where all times are valid for checks,

# notifications, etc. The classic 24x7 support nightmare. :-) timeperiod {_name 24x724 Hours A Day, 7 Days A Week00: 00-24: 0000: 00-24: 0000: 00-24: 0000: 00-24: 0000: 00-24: 0000: 00-24: 0000: 00-24: 00

}


# workhours timeperiod definitiontimeperiod {_name workhoursNormal Work Hours09: 00-18: 0009: 00-18: 0009: 00-18: 0009: 00-18: 0009: 00-18: 00

}


# none timeperiod definitiontimeperiod {_name noneNo Time Is A Good Time

}


# Some U.S. holidays

# Note: The timeranges for each holiday are meant to * exclude * the holidays from being

# treated as a valid time for notifications, etc. You probably do not want yo...


Назад | сторінка 34 з 65 | Наступна сторінка





Схожі реферати:

  • Реферат на тему: National Health Service in Great Britain
  • Реферат на тему: Розробка служби Service Desk АТ &Алюміній Казахстану&
  • Реферат на тему: Організація служби Room-service в готелі &Німецький клуб&
  • Реферат на тему: Розробка програми в середовищі операційної системи Windows XP Professional ...
  • Реферат на тему: Парсер курсів валют українських банків, створене на Основі Windows Service