[Nagios-users] Dealing with nightly high load
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
Re: [Nagios-users] Escalations causing "Recover" messages with noproblem message send
Gents,
Posted this about a week ago and it's starting to become a real problem
for us. We receive regular "recovery" message without getting any
Warning/Criticals. Any help would be highly appreciated.
Met vriendelijke groet/With kind regards,
Jasper Filon
CAIWAY Business
-Oorspronkelijk bericht-
Van: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Namens Jasper Filon
Verzonden: woensdag 21 november 2007 9:13
Aan: nagios-users@lists.sourceforge.net
Onderwerp: [Nagios-users] Escalations causing "Recover" messages with
noproblem message send
Dear All,
I'm implementing Nagios for a large ISP in the Netherlands. I configured
all service-notifications to be sent to both the "linux-admin" group and
the "linux-admin-sms" group. The first is by email, the second by sms.
The Linux-admin-sms is set to only accept C, U and R (critical, unknown,
recovered) messages for services.
We want the first notification that something is wrong (either critical
or warning) not by sms, but only by email. In order to keep
configuration as easy as possible and minimizing the work of adding a
new host, I simply made an service "escalation" stating:
## All first notifications only go by email define serviceescalation{
host_name *
service_description *
contact_groups linux-admins;
first_notification 1
last_notification 1
notification_interval 15
}
This works fine and causes the first message to be only send by Email.
Any Critical message beyond the first goes by sms as well as intented.
This has an unintended side-effect in case the services goed through the
following sequence:
- Service goes critical -> notification by email (first notification)
- Service goes warning -> notification by email (2nd allert, but no sms
is send for warnings)
- Service goes ok -> recovery notification by email _and
by sms_
Obviously, it is unwanted that a recovery message is send out by SMS in
this case, because the recipient didnt know there was a problem in the
first place. According to the documentation, this should not be
possible:
http://nagios.sourceforge.net/docs/2_0/notifications.html#contacts
Note: Notifications about host or service recoveries are only sent out
if a notification was sent out for the original problem. It doesn't make
sense to get a recovery notification for something you never knew was a
problem...
Can somebody give me more information regarding the way Nagios handles
notifications? I thought the above url explained everything clearly but
it doesnt explain this problem.
Any help appreciated.
Met vriendelijke groet/With kind regards,
Jasper Filon
CAIWAY Business
-
This SF.net email is sponsored by: Microsoft Defy all challenges.
Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
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
--
Deze email is gecontroleerd door CAIWAY Internet Virusvrij.
Voor meer informatie, zie http://www.caiway.nl/
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
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] Escalations causing "Recover" messages with no problem message send
Dear All,
I'm implementing Nagios for a large ISP in the Netherlands. I configured
all service-notifications to be sent to both the "linux-admin" group and
the "linux-admin-sms" group. The first is by email, the second by sms.
The Linux-admin-sms is set to only accept C, U and R (critical, unknown,
recovered) messages for services.
We want the first notification that something is wrong (either critical
or warning) not by sms, but only by email. In order to keep
configuration as easy as possible and minimizing the work of adding a
new host, I simply made an service "escalation" stating:
## All first notifications only go by email
define serviceescalation{
host_name *
service_description *
contact_groups linux-admins;
first_notification 1
last_notification 1
notification_interval 15
}
This works fine and causes the first message to be only send by Email.
Any Critical message beyond the first goes by sms as well as intented.
This has an unintended side-effect in case the services goed through the
following sequence:
- Service goes critical -> notification by email (first notification)
- Service goes warning -> notification by email (2nd allert, but no sms
is send for warnings)
- Service goes ok -> recovery notification by email _and
by sms_
Obviously, it is unwanted that a recovery message is send out by SMS in
this case, because the recipient didnt know there was a problem in the
first place. According to the documentation, this should not be
possible:
http://nagios.sourceforge.net/docs/2_0/notifications.html#contacts
Note: Notifications about host or service recoveries are only sent out
if a notification was sent out for the original problem. It doesn't make
sense to get a recovery notification for something you never knew was a
problem...
Can somebody give me more information regarding the way Nagios handles
notifications? I thought the above url explained everything clearly but
it doesnt explain this problem.
Any help appreciated.
Met vriendelijke groet/With kind regards,
Jasper Filon
CAIWAY Business
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
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
