Re: [Nagios-users] skip monitoring every 4 weeks

2009-01-29 Thread Edgar Matzinger
Hi Assaf,

 
 I have a situation where i need to turn of monitoring for server while
 they are being rebooted ,
 this is done during the weekend , and the person doing the reboots is
 not one that has access to
 the nagios .


  why don't you specify downtimes? For those hosts? This can be done
in advance.

HTH, cu l8r, Edgar.
-- 
|\  /| :: Addr: Valid Eindhoven B.V.
 /  | \/ | : Edgar R. Matzinger :   t.a.v. E.R. Matzinger
/   || ::   Paradijslaan 36
\  /|  /\| ::   5611 KN Eindhoven
 \/   /  \ : Valid Eindhoven BV :
  \  /\  / ::
   \/ |\/  ::
  |::
Disclaimer: Any comments, opinions made are mine, etc ... 


--
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
___
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


Re: [Nagios-users] skip monitoring every 4 weeks

2009-01-29 Thread Andreas Ericsson
Assaf Flatto wrote:
 Hello 
 
 I have a situation where i need to turn of monitoring for server while they 
 are being rebooted , 
 this is done during the weekend , and the person doing the reboots is not one 
 that has access to
 the nagios .
 
 i know that Version 3 placed the functionality of alternating and dynamic 
 scheduling in the 
 timeperiods definitions , but after reading the online documentation , i'm 
 not realy clear on ho i 
 can achieve my gaol.
 
 I need the monitoring for a server to be stopped during a period (specific 
 times TBD ) every 4th 
 weekend , (Sunday or Saturday , again yet to be determined ).
 
 I understand that I need to define a time period and add an exclude  to the 
 time period the host 
 in question has defined .
 
 My issue is with the correct format of the skipped timeperiod .
 Is what I'm defining below correct in format and functionality  - if not in 
 strict content  ?
 
 define timeperiod{
timeperiod_name weekend-off
Sunday /28  00:00-24:00
}
 

I'm not 100% sure, but I *think* you want to use 

Sunday -1 00:00-24:00

if you mean last sunday of the month.

 define timeperiod{
timeperiod_name box-reboot
use 24x7
exclude offweekend
 }
 

The rest looks good though.

-- 
Andreas Ericsson   andreas.erics...@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225  Fax: +46 8-230231

--
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
___
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


Re: [Nagios-users] skip monitoring every 4 weeks

2009-01-29 Thread Assaf Flatto

On Thursday 29 January 2009 13:41:46 Edgar Matzinger wrote:
 Hi Assaf,

  I have a situation where i need to turn of monitoring for server while
  they are being rebooted ,
  this is done during the weekend , and the person doing the reboots is
  not one that has access to
  the nagios .

   why don't you specify downtimes? For those hosts? This can be done
 in advance.

 HTH, cu l8r, Edgar.

Cause the whole idea is to make it automatic and dynamic and not to find out 
after the weekend that 
we forgot to set the scheduled down time in the nagios .
and as i said - it is not every weekend, but once in 4 weeks.

Assaf

-- 
Assaf Flatto
SSP Ops Team
Linux System Administrator
169 Euston Road, London, NW1 2AE





IMPORTANT . this email and the information in it may be confidential, legally
privileged and/or protected by law. It is intended solely for the use of the
person to whom it is addressed. If you are not the intended recipient, please
notify the sender immediately and do not disclose the contents to any other
person, use it for any purpose, or store or copy the information in any medium.
Please also delete all copies of this email and any attachments from your
system.

We cannot guarantee the security or confidentiality of email communications. We
do not accept any liability for losses or damages that you may suffer as a
result of your receipt of this email including but not limited to computer
service or system failure, access delays or interruption, data non-delivery or
mis-delivery, computer viruses or other harmful components.

Copyright in this email and any attachments belong to Select Service Partner UK
Limited. Should you communicate with anyone at Select Service Partner UK 
Limited by
email, you consent to us monitoring and reading any such correspondence.

Nothing in this email shall be taken or read as suggesting, proposing or
relating to any agreement concerted practice or other practice that could
infringe UK or EC competition legislation.

Select Service Partner UK Limited is a company registered in England and Wales
(company number 05687183) whose registered office is at 1 The Heights, 
Brooklands, Weybridge. Surrey. KT13 0NY
 
 

--
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
___
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


Re: [Nagios-users] skip monitoring every 4 weeks

2009-01-29 Thread Kevin Keane
What you are describing is, in more generic terms, a maintenance window.

I'm actually using a very different approach for the same basic problem:
I schedule downtime for that maintenance window. Now Nagios doesn't
support recurring scheduled downtimes directly. The solution is a script
(this one has hardcoded 2 hours scheduled downtime - change as needed).

#!/bin/bash
# schedules downtime for the host given in $1

now=$(date +%s)
read host
read comment

# the host may need to be capitalized. To find the correct version,
parse the Nagios config files:
fixed_host=$(grep -ri host_name.*$host /etc/nagios/objects | uniq |
awk '{ print $3; }')

NAGIOSCMD=[$now]
SCHEDULE_AND_PROPAGATE_TRIGGERED_HOST_DOWNTIME;$fixed_host;$now;$(($now+7200));1;0;7200;Kevin
 

Keane;$comment
echo -e $NAGIOSCMD \n  /var/spool/nagios/nagios.cmd

In my case, the backup script also calls this one. You may instead want
to use cron, or you could invoke it from a shutdown script in the server
being rebooted, remotely via ssh.



Assaf Flatto wrote:
 Hello 

 I have a situation where i need to turn of monitoring for server while they 
 are being rebooted , 
 this is done during the weekend , and the person doing the reboots is not one 
 that has access to
 the nagios .

 i know that Version 3 placed the functionality of alternating and dynamic 
 scheduling in the 
 timeperiods definitions , but after reading the online documentation , i'm 
 not realy clear on ho i 
 can achieve my gaol.

 I need the monitoring for a server to be stopped during a period (specific 
 times TBD ) every 4th 
 weekend , (Sunday or Saturday , again yet to be determined ).

 I understand that I need to define a time period and add an exclude  to the 
 time period the host 
 in question has defined .

 My issue is with the correct format of the skipped timeperiod .
 Is what I'm defining below correct in format and functionality  - if not in 
 strict content  ?

 define timeperiod{
timeperiod_name weekend-off
Sunday /28  00:00-24:00
}

 define timeperiod{
timeperiod_name box-reboot
use 24x7
exclude offweekend
 }


 Thanks


   


-- 
Kevin Keane
Owner
The NetTech
Find the Uncommon: Expert Solutions for a Network You Never Have to 
Think About

Office: 866-642-7116
http://www.4nettech.com

This e-mail and attachments, if any, may contain confidential and/or 
proprietary information. Please be advised that the unauthorized use or 
disclosure of the information is strictly prohibited. The information 
herein is intended only for use by the intended recipient(s) named 
above. If you have received this transmission in error, please notify 
the sender immediately and permanently delete the e-mail and any copies, 
printouts or attachments thereof.

--
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
___
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