Re: [Nagios-users] Dealing with nightly high load

2007-11-29 Thread mark . potter
Cell: 281-734-6965


[EMAIL PROTECTED] wrote on 11/29/2007 02:30:20 
AM:

> All,
> 
> I'm trying to deal with a bunch of servers that generate some high load
> during the night. That is, between 00:00 and 06:00 a series of job is
> run that will generate load from 10 to 15. Outside this windows, load
> should be no more than 3.
> 
> I have read all the documentation, but I cant find a way to implement
> this in Nagios. I have found 2 options:
> - defining 2 services (load_daily and load_nightly) with different
> tresholds. This will make 2 services show up in nagios that are
> essential the same
> - using escalations to supress messages during the night. This will
> however still show errors in the webinterface and spoil you reports with
> fake errors
> 
> How can I tell Nagios that during the day the load should be max 3
> (warning) and max 5 (critical) but during the night, it's ok if they are
> 8 (warning) and 10 (critical)? I'm sure other people have ran into this
> same problem and found a solution for it? Please share!
> 
> I'm running Nagios 2.10
> 
> Thanx for the help.
> 
> Met vriendelijke groet/With kind regards, 
> 
> Jasper Filon
> 
> CAIWAY Business
> 


Jasper,

I have sort of the same issue and you have already stated the most 
expedient, and indeed only, solution that I found. Two services with 
different time periods for checking. It's doesn't look as pretty in the 
web interface but it works like a charm. The other method would be to 
write a wrapper that performs the check and alerts on the value you set 
based on time. This wouldn't be hard to do to be honest but it seems like 
re-inventing the wheel to some degree. The other question I have is if the 
servers are capable of withstanding a load that high why not just have 
your high threshold set the same all time? My situation isn't load based 
but with the standard Nagios plugin you can alert on any of the three 
points that uptime returns (here I make the assumption you are monitoring 
*nix boxen). If the situation calls for being able to be alerted to spikes 
during normal operating hours then you will either need two checks and 
time period for each or a wrapper that checks the time and returns an 
alert based on the time and load.

Best Regards,

Mark L. Potter
-
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell.  From the desktop to the data center, Linux is going
mainstream.  Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4___
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] Dealing with nightly high load

2007-11-29 Thread Duncan Ferguson

On 29 Nov 2007, at 08:30, Jasper Filon wrote:

> All,
>
> I'm trying to deal with a bunch of servers that generate some high  
> load
> during the night. That is, between 00:00 and 06:00 a series of job is
> run that will generate load from 10 to 15. Outside this windows, load
> should be no more than 3.
>

http://altinity.blogs.com/dotorg/2007/04/changing_a_serv.html

It works for us...

   Duncs

-- 
Duncan Ferguson
Senior Developer, Altinity Limited

http://www.altinity.com
Tel: +44 (0)870 787 9243
US:  +1 866 879 9184
Fax: +44 (0)845 280 1725
Skype: duncan_j_ferguson
MSN: [EMAIL PROTECTED]

The contents of this email and any files transmitted with it are  
confidential and intended solely for the use of the individuals to  
whom it is addressed.
If you are not the intended recipient or have received this e-mail in  
error please notify the sender and delete this e-mail immediately.
Any unauthorised copying, disclosure or distribution of the material  
in this e-mail is strictly prohibited.

Altinity Limited | 404 Seven Sisters Road | London | N4 2LX | United  
Kingdom
Registered in England and Wales under company number 4743767


-
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell.  From the desktop to the data center, Linux is going
mainstream.  Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
___
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


[Nagios-users] Dealing with nightly high load

2007-11-29 Thread Jasper Filon
All,

I'm trying to deal with a bunch of servers that generate some high load
during the night. That is, between 00:00 and 06:00 a series of job is
run that will generate load from 10 to 15. Outside this windows, load
should be no more than 3.

I have read all the documentation, but I cant find a way to implement
this in Nagios. I have found 2 options:
- defining 2 services (load_daily and load_nightly) with different
tresholds. This will make 2 services show up in nagios that are
essential the same
- using escalations to supress messages during the night. This will
however still show errors in the webinterface and spoil you reports with
fake errors

How can I tell Nagios that during the day the load should be max 3
(warning) and max 5 (critical) but during the night, it's ok if they are
8 (warning) and 10 (critical)? I'm sure other people have ran into this
same problem and found a solution for it? Please share!

I'm running Nagios 2.10

Thanx for the help.

Met vriendelijke groet/With kind regards, 

Jasper Filon

CAIWAY Business

-
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell.  From the desktop to the data center, Linux is going
mainstream.  Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
___
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