Hi ,
First all, sorry by english..
So, Is there any relation between freshness_threshold and timeperiods?
For example:
define timeperiod{
timeperiod_name backup_hours
alias Backup hours
monday 05:00-24:00
tuesday 00:00-24:00
wednesday 00:00-24:00
thursday00:00-24:00
friday 00:00-24:00
saturday00:00-05:00
}
define service{
service_description BACKUP1
host_name host1
active_checks_enabled 0
passive_checks_enabled 1
parallelize_check 1
obsess_over_service 1
check_freshness 1
freshness_threshold 93600
notifications_enabled 1
event_handler_enabled 1
flap_detection_enabled 1
is_volatile 0
max_check_attempts 1
check_periodbackup_hours
normal_check_interval 1
retry_check_interval1
notification_interval 120
notification_period 24x7
notification_optionsw,c,r
contact_groups backup_operators
process_perf_data 1
retain_status_information 1
retain_nonstatus_information1
check_command no_backup_report!26!hours
}
All is work fine.. But...
Let me try to explain my problem:
- Backup OK status: Saturday 03:00pm
- The backup services aren't executed on Sundays
(timeperiod=backup_hours)
- But in monday, at the morning, I recived alerts from Nagios, because
the
freshness_threshold limit (26 hours)
- But sundays hours don't should be count, right?
So, what can I do for Nagios respect de time_period on passive checks??
Rejaine
---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
___
Nagios-users mailing list
Nagios-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting
any issue.
::: Messages without supporting info will risk being sent to /dev/null