Re: [Nagios-users] Escalation issues

[Alex]

Hi,

>> I have also interval_length=60 in nagios.cfg. I don't understand why
>> admins-escal isn't consulted after three consecutive attempts at
>> communicating with the service. What am I doing wrong?
>
> This is a silly question, but are there contacts who are members of the 
> admins-escal group?  And do they have service_notification_options that 
> overlap the ones defined in your escalation?
>
> I haven't tried using templates for escalations yet.  Have you tried defining 
> an escalation without using a template?
>
> Does the config page for service escalations show anything?  The URL would 
> end up being something like:
> http://your_nagios_host/nagios/cgi-bin/config.cgi?type=serviceescalations&expand=mailhost

Thanks for the info. I've ended up almost completely rebuilding the
configuration, trying to understand how it all works and get
notifications working, and stop alerting either too late or too many
times.

I have something that at least works now, but I'm continuing to make
changes to improve it.

Thanks again,
Alex

--
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and 
their applications. This 200-page book is written by three acclaimed 
leaders in the field. The early access version is available now. 
Download your free book today! http://p.sf.net/sfu/neotech_d2d_may
___
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] Escalation issues

[Chris Beattie]

On 5/5/2013 11:29 PM, Alex wrote:
> I have also interval_length=60 in nagios.cfg. I don't understand why
> admins-escal isn't consulted after three consecutive attempts at
> communicating with the service. What am I doing wrong?

This is a silly question, but are there contacts who are members of the 
admins-escal group?  And do they have service_notification_options that overlap 
the ones defined in your escalation?

I haven't tried using templates for escalations yet.  Have you tried defining 
an escalation without using a template?

Does the config page for service escalations show anything?  The URL would end 
up being something like:
http://your_nagios_host/nagios/cgi-bin/config.cgi?type=serviceescalations&expand=mailhost

-- 
-Chris

--
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and 
their applications. This 200-page book is written by three acclaimed 
leaders in the field. The early access version is available now. 
Download your free book today! http://p.sf.net/sfu/neotech_d2d_may
___
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] Escalation issues

[Alex]

Hi all,

I have a working nagios system on fc17, but I don't think I have the
escalations configured properly. I have the following service
templates defined:

At what point are the services converted to being escalated services
in my sample below?

define service {
namestandard-service-24x7
active_checks_enabled   1
passive_checks_enabled  1
parallelize_check   1
obsess_over_service 1
check_freshness 0
notifications_enabled   1
event_handler_enabled   1
flap_detection_enabled  1
process_perf_data   1
retain_status_information   1
retain_nonstatus_information1
max_check_attempts  5

# number of min between checks
normal_check_interval   4
retry_check_interval1
is_volatile 0
check_period24x7
contact_groups  admins

# re-notify every ten minutes
notification_interval   10
notification_period 24x7
notification_optionsw,u,c,r
register0
}

define serviceescalation {
namecritical-services
first_notification  3
last_notification   10
#contact_groups linux-admins,noc-admins,techs-phones
contact_groups  admins-escal
notification_interval   10
register0
}

I also have a number of services configured such as this:

define service {
use standard-service-24x7
host_name   mailhost
service_description MAILQ-pre
check_command   check-host-alive
}

define serviceescalation {
use critical-services
host_name   mailhost
service_description MAILQ-pre
}

I have also interval_length=60 in nagios.cfg. I don't understand why
admins-escal isn't consulted after three consecutive attempts at
communicating with the service. What am I doing wrong?

Thanks,
Alex

--
Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET
Get 100% visibility into your production application - at no cost.
Code-level diagnostics for performance bottlenecks with <2% overhead
Download for free and get started troubleshooting in minutes.
http://p.sf.net/sfu/appdyn_d2d_ap1
___
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] Escalation

[aragonx]

Hi,

I have a bunch of things I would like to do with
notification and I'm not sure it's possible. 

First, let me
make sure I understand how this works.  For any notification, only
one group will be notified.  Is that correct?

Anyway, we
have admins that I want to be notified via email during the day (7am-5pm)
for d, u, w or c, u, w.  During the evening, I want only c or d to go
to a pager.  On the 5th notification and after, I want alerts to go
to a different pager.  On the 9th notification and after, I want
alerts to go to the 2nd pager and a 3rd pager.

This doesn't
seem to be working for me.  Here is what I have.  Can someone
please tell me what I'm doing wrong?

define contact{
   
contact_name                   
nagiosadmin         ; Short name
of user
   
use                            
generic-contact     ; Inherit default values from
generic-contact template (defined above)
   
alias                          
Nagios Admin        ; Full name of
user
   
email                          
nob...@nowhere.com
   
host_notification_period       
daytime
   
service_notification_period     daytime
    }

define contact{
   
contact_name                   
adminpager          ; Short
name of user
   
use                            
generic-contact     ; Inherit default values from
generic-contact template (defined above)
   
alias                          
Admin Pager         ; Full name of
user
   
email                          
000...@nowhere.com
   
host_notification_options       d, u
    service_notification_options    c,
u
   
host_notification_period        24x7
    service_notification_period    
24x7
    }

define contact{
   
contact_name                   
oncallpager
   
use                            
generic-contact
   
alias                          
Oncall Pager
   
email                          
000...@nowhere.com
   
host_notification_options       d, u
    service_notification_options    c,
u
   
host_notification_period        24x7
    service_notification_period    
24x7
    }

define contact{
   
contact_name                   
managerpager
   
use                            
generic-contact
   
alias                          
Manager's Pager
   
email                          
000...@nowhere.com
   
host_notification_options       d, u
    service_notification_options    c,
u
   
host_notification_period        24x7
    service_notification_period    
24x7
    }

define serviceescalation{
   
hostgroup_name                 
windows-xp-servers, windows-servers, unix-servers
   
contacts                       
managerpager
   
first_notification             
6
   
last_notification              
0
   
notification_interval          
15
   
escalation_period              
24x7
   
escalation_options             
w,u,c,r
    }

define hostescalation{
   
hostgroup_name                 
windows-xp-servers, windows-servers, unix-servers
   
contacts                       
managerpager
   
first_notification             
6
   
last_notification              
0
   
notification_interval          
15
   
escalation_period              
24x7
   
escalation_options             
d,u,r
    }

define serviceescalation{
   
hostgroup_name                 
windows-xp-servers, windows-servers, unix-servers
   
contacts                       
adminpager
   
first_notification             
2
   
last_notification              
0
   
notification_interval          
15
   
escalation_period              
daytime
   
escalation_options             
w,u,c,r
    }
define hostescalation{
   
hostgroup_name                 
windows-xp-servers, windows-servers, unix-servers
   
contacts                       
adminpager
   
first_notification             
2
   
last_notification              
0
   
notification_interval          
15
   
escalation_period              
daytime
   
escalation_options  Â

Re: [Nagios-users] escalation question

[michal . lackovic]

Many thanks Terry ! It works like a charm now

Michal






Terry  
10/11/2010 03:31 PM
Please respond to
Nagios Users List 


To
Nagios Users List 
cc

Subject
Re: [Nagios-users] escalation question






On Mon, Oct 11, 2010 at 3:48 AM,
 wrote:
> Hi All,
>
> Is there any way how to create service escalation in the following way:
>
> hostgroup_nameGroup1,Group2
> service_description*
> contact_groupManagers
>
> Basically I would need to escalate all service problems on the hosts 
which
> are members of Group1 and Group2 to the managers.
>
> thanks in advance
> Michal
>
> 
--

Yes, you're exactly right.  We took it a step further and put all
hosts in a single group then globbed it as you did above:

define serviceescalation{
hostgroup_name  allhosts
service_description .*
contactsfoo,foo2
first_notification  1
last_notification   1
notification_interval   1
escalation_options  w,u,c
}
define hostgroup {
hostgroup_name  allhosts
alias   allhosts
members .*
}
use_regexp_matching=1

I think that's all you need to enable globbing.

--
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
Spend less time writing and  rewriting code and more time creating great
experiences on the web. Be a part of the beta today.
http://p.sf.net/sfu/beautyoftheweb
___
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

__
This email has been scanned by the MessageLabs Email Security System.
__

--
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
Spend less time writing and  rewriting code and more time creating great
experiences on the web. Be a part of the beta today.
http://p.sf.net/sfu/beautyoftheweb___
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] escalation question

[Terry]

On Mon, Oct 11, 2010 at 4:02 PM, Paul M. Dubuc  wrote:
> Terry wrote:
>>
>> On Mon, Oct 11, 2010 at 3:48 AM,
>>   wrote:
>>>
>>> Hi All,
>>>
>>> Is there any way how to create service escalation in the following way:
>>>
>>> hostgroup_name                Group1,Group2
>>> service_description                *
>>> contact_group                        Managers
>>>
>>> Basically I would need to escalate all service problems on the hosts
>>> which
>>> are members of Group1 and Group2 to the managers.
>>>
>>> thanks in advance
>>> Michal
>>>
>>>
>>> --
>>
>> Yes, you're exactly right.  We took it a step further and put all
>> hosts in a single group then globbed it as you did above:
>>
>> define serviceescalation{
>>         hostgroup_name          allhosts
>>         service_description     .*
>>         contacts                foo,foo2
>>         first_notification      1
>>         last_notification       1
>>         notification_interval   1
>>         escalation_options      w,u,c
>>         }
>> define hostgroup {
>>         hostgroup_name  allhosts
>>         alias           allhosts
>>         members         .*
>>         }
>> use_regexp_matching=1
>>
>> I think that's all you need to enable globbing.
>
> Thanks for this example.
>
> I'm trying to do something similar with an allhosts hostgroup definition and
> it doesn't seem to work unless all hosts in the allhosts group also have
> services defined for them.  In this case I get an error like
>
> Error: Could not find a service matching host name 'AXSP51' and description
> '.*' (config file
> '/vol/omni/nagios-3.2.1/config/test/objects/contacts/Contacts.cfg', starting
> on line 74)
> Error: Could not expand services specified in service escalation (config
> file '/vol/omni/nagios-3.2.1/config/test/objects/contacts/Contacts.cfg',
> starting on line 74)
>
> AXSP51 has no services defined for it, but I monitor it as a parent for
> hosts that do.  Do I need to maintain a host group to use instead of
> allhosts just for the hosts that have services defined for them, or is there
> a more convenient (i.e., less error prone) way around this?
>
> Thanks,
> Paul Dubuc
>
>

I just created a passive check to get around this if I remember correctly:

define service{
hostgroup_name  allhosts
service_description trap
servicegroups   trap
is_volatile 1
flap_detection_enabled  0
active_checks_enabled   0
passive_checks_enabled  1
max_check_attempts  1
check_period24x7
check_command   check_none
}

--
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
Spend less time writing and  rewriting code and more time creating great
experiences on the web. Be a part of the beta today.
http://p.sf.net/sfu/beautyoftheweb
___
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] escalation question

[Paul M. Dubuc]

Terry wrote:
> On Mon, Oct 11, 2010 at 3:48 AM,
>   wrote:
>> Hi All,
>>
>> Is there any way how to create service escalation in the following way:
>>
>> hostgroup_nameGroup1,Group2
>> service_description*
>> contact_groupManagers
>>
>> Basically I would need to escalate all service problems on the hosts which
>> are members of Group1 and Group2 to the managers.
>>
>> thanks in advance
>> Michal
>>
>> --
>
> Yes, you're exactly right.  We took it a step further and put all
> hosts in a single group then globbed it as you did above:
>
> define serviceescalation{
>  hostgroup_name  allhosts
>  service_description .*
>  contactsfoo,foo2
>  first_notification  1
>  last_notification   1
>  notification_interval   1
>  escalation_options  w,u,c
>  }
> define hostgroup {
>  hostgroup_name  allhosts
>  alias   allhosts
>  members .*
>  }
> use_regexp_matching=1
>
> I think that's all you need to enable globbing.

Thanks for this example.

I'm trying to do something similar with an allhosts hostgroup definition and 
it doesn't seem to work unless all hosts in the allhosts group also have 
services defined for them.  In this case I get an error like

Error: Could not find a service matching host name 'AXSP51' and description 
'.*' (config file 
'/vol/omni/nagios-3.2.1/config/test/objects/contacts/Contacts.cfg', starting 
on line 74)
Error: Could not expand services specified in service escalation (config file 
'/vol/omni/nagios-3.2.1/config/test/objects/contacts/Contacts.cfg', starting 
on line 74)

AXSP51 has no services defined for it, but I monitor it as a parent for hosts 
that do.  Do I need to maintain a host group to use instead of allhosts just 
for the hosts that have services defined for them, or is there a more 
convenient (i.e., less error prone) way around this?

Thanks,
Paul Dubuc


--
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
Spend less time writing and  rewriting code and more time creating great
experiences on the web. Be a part of the beta today.
http://p.sf.net/sfu/beautyoftheweb
___
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] escalation question

[Terry]

On Mon, Oct 11, 2010 at 3:48 AM,
 wrote:
> Hi All,
>
> Is there any way how to create service escalation in the following way:
>
> hostgroup_name                Group1,Group2
> service_description                *
> contact_group                        Managers
>
> Basically I would need to escalate all service problems on the hosts which
> are members of Group1 and Group2 to the managers.
>
> thanks in advance
> Michal
>
> --

Yes, you're exactly right.  We took it a step further and put all
hosts in a single group then globbed it as you did above:

define serviceescalation{
hostgroup_name  allhosts
service_description .*
contactsfoo,foo2
first_notification  1
last_notification   1
notification_interval   1
escalation_options  w,u,c
}
define hostgroup {
hostgroup_name  allhosts
alias   allhosts
members .*
}
use_regexp_matching=1

I think that's all you need to enable globbing.

--
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
Spend less time writing and  rewriting code and more time creating great
experiences on the web. Be a part of the beta today.
http://p.sf.net/sfu/beautyoftheweb
___
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] escalation question

[michal . lackovic]

Hi All,

Is there any way how to create service escalation in the following way:

hostgroup_name  Group1,Group2
service_description *
contact_group   Managers

Basically I would need to escalate all service problems on the hosts which 
are members of Group1 and Group2 to the managers.

thanks in advance
Michal
--
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
Spend less time writing and  rewriting code and more time creating great
experiences on the web. Be a part of the beta today.
http://p.sf.net/sfu/beautyoftheweb___
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] Escalation question

[Martin Melin]

On Wed, May 19, 2010 at 3:20 PM, Vladimir N. Indik
 wrote:
> I want to send notification to three contacts in order.
> o...@example.com
> wait 10 minutes
> t...@example.com
> wait 10 minutes
> th...@example.com
>
> My config:
> define service {
>        host_name                       hostname
>        service_description             servicename
>        notification_interval           600              #!
>        max_check_attempts              2               #!
>        flap_detection_enabled          0
>        contacts                        ...@example.com
> }
>
> define serviceescalation{
>        host_name                       hostname
>        service_description             servicename
>        first_notification              2
>        last_notification               2
>        notification_interval           600
>        contacts                        ...@example.com
>        }
>
> define serviceescalation{
>        host_name                       facts
>        service_description             Facts test
>        first_notification              3
>        last_notification               3
>        notification_interval           0
>        contacts                        th...@example.com
>        }
>
> Is it all rihtg?
>
> I have a problem with this configuration.
> When the status changes to OK, the message about it only receives the last
> contact (e.g. th...@example.com). This is a bug?
>

No, it is working as designed. Read up on how escalations work here:
http://nagios.sourceforge.net/docs/3_0/escalations.html

It is considered best practice to include contacts from lower
escalation ranges in higher escalations, because of this exact issue.

Quote the above doc:

"When defining notification escalations, it is important to keep in
mind that any contact groups that were members of "lower" escalations
(i.e. those with lower notification number ranges) should also be
included in "higher" escalation definitions. This should be done to
ensure that anyone who gets notified of a problem continues to get
notified as the problem is escalated. "

Best regards,
Martin Melin

--

___
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] Escalation question

[Vladimir N. Indik]

I want to send notification to three contacts in order.
o...@example.com
wait 10 minutes
t...@example.com
wait 10 minutes
th...@example.com

My config:
define service {
host_name   hostname
service_description servicename
notification_interval   600  #!
max_check_attempts  2   #!
flap_detection_enabled  0
contactso...@example.com
}

define serviceescalation{
host_name   hostname
service_description servicename
first_notification  2
last_notification   2
notification_interval   600
contactst...@example.com
}

define serviceescalation{
host_name   facts
service_description Facts test
first_notification  3
last_notification   3
notification_interval   0
contactsth...@example.com
}

Is it all rihtg?

I have a problem with this configuration.
When the status changes to OK, the message about it only receives the last 
contact (e.g. th...@example.com). This is a bug?

--

___
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] Escalation in Host / Service Definitions?

[Chris Pepper]

To keep things simple, we define contacts in our host templates. This 
means that adding a simple host is as simple as copying & pasting a short host 
definition and changing the name. I'd like to do the same for escalations -- 
sending to the same people's cellphones via email, at least for now.

We definitely don't want to add a hostname to hostnameescalation & 
serviceescalation definitions every time we add a host (in another file).

Is there any particular reason hosts can define contacts but not 
escalations? This applies equally to services, of course.

For now, I will define hostgroups inside serviceescalation, but I'm not 
sure how that will affect additional contacts (added with +user in individual 
host & hostgroup definitions).

Alternatively, if there's a simple way to start with email 
notifications and then automatically start pager notifications (for those 
contacts with pager: defined) after an interval, that would work as well and be 
even simpler. I don't see anything built in for deferring pages until a few 
emails have gone unanswered, though.

Thanks!

Chris Pepper

> define host {
> namelinux-server
> usegeneric-host
> check_period24x7
> check_interval5
> retry_interval1
> max_check_attempts10
> check_commandcheck-host-alive
> notification_period24x7
> notification_interval30
> notification_optionsd,u,r
> contact_groupsadmins
> register0
> hostgroupslinux-servers, ssh-disks-monitored, ssh-load-monitored
> }

-- 
Chris Pepper:
 

--
SOLARIS 10 is the OS for Data Centers - provides features such as DTrace,
Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW
http://p.sf.net/sfu/solaris-dev2dev
___
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] Escalation notification count and state change problem

[Neil Ramsay]

Hi,

I've searched and found similar posts but unfortunately no replies to this
type of problem. I'd expect this to be a common problem but maybe I've
misread the documentation.

On Nagios 3.2.0 we have service notifications set to go out for Warning and
for Critical states to an email address 24x7.

In addition during 'after hours', the on-call engineer receives SMS alerts
for all Critical notifications and the backup engineer should receive
escalations after the 4th Critical notification. However, last night the
backup engineer received an SMS on the second Critical notification.


define serviceescalation{
hostgroup_name switches,primary_nodes,secondary_nodes
service_description *
first_notification 4
last_notification 0
notification_interval 5
contact_groups  PrimaryAH,SecondaryAH
escalation_period afterhours
escalation_options u,c
}

# Primary After-hours contacts
define contactgroup{
contactgroup_name   PrimaryAH
alias   Primary After-Hours contact
members supportEmail,Engineer1
}

# Secondary After-hours contacts
define contactgroup{
contactgroup_name   SecondaryAH
alias   Secondary After-Hours contact
members supportEmail,Engineer2
}





It appears that escalation procedure ignores the actual sate when counting
notifications. So if the 1st notification is critical and the 4th is
critical but 2-3 are Warnings the 4th notification is escalated as it is
critical. Eventhough only 1 critical notification was sent and the other 2
were warnings. I was hoping that on the 4th critical notification Nagios
escalates.

See event log below:

Service Notification [10-26-2009 23:48:32] SERVICE NOTIFICATION:
Engineer2;winapps1;NT memory usage;CRITICAL;notify-service-by-sms;Mem: 984
MB (96%) / 1023 MB (3%) Paged Mem: 1189 MB (48%) / 2469 MB (51%)

Service Notification[10-26-2009 23:48:32] SERVICE NOTIFICATION:
Engineer1;winapps1;NT memory usage;CRITICAL;notify-service-by-sms;Mem: 984
MB (96%) / 1023 MB (3%) Paged Mem: 1189 MB (48%) / 2469 MB (51%



Service Notification[10-26-2009 23:38:32] SERVICE NOTIFICATION:
supportEmail;winapps1;NT memory usage;WARNING;notify-service-by-email;Mem:
950 MB (92%) / 1023 MB (7%) Paged Mem: 1219 MB (49%) / 2469 MB (50%)


Service Notification[10-26-2009 23:28:32] SERVICE NOTIFICATION:
supportEmail;winapps1;NT memory usage;WARNING;notify-service-by-email;Mem:
881 MB (86%) / 1023 MB (13%) Paged Mem: 1192 MB (48%) / 2469 MB (51%)


Service Notification[10-26-2009 23:18:32] SERVICE NOTIFICATION:
supportEmail;winapps1;NT memory usage;CRITICAL;notify-service-by-email;Mem:
1006 MB (98%) / 1023 MB (1%) Paged Mem: 1152 MB (46%) / 2469 MB (53%)

Service Notification[10-26-2009 23:18:32] SERVICE NOTIFICATION:
Engineer1;winapps1;NT memory usage;CRITICAL;notify-service-by-sms;Mem: 1006
MB (98%) / 1023 MB (1%) Paged Mem: 1152 MB (46%) / 2469 MB (53%)


Is there a way to avoid this behaviour?

Thanks

Neil
--
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference___
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] escalation for receiving only recovery events?

[shadih rahman]

The best solution would be service escalation or host escalation feature of
nagios.


http://books.google.com/books?id=Iujcg9s3BKMC&pg=PA262&lpg=PA262&dq=service+escalation+nagios&source=bl&ots=Ppge7Pp9sa&sig=slpkoN27AccERQP5l0b1tvJy4p4&hl=en&ei=UPfLSryoG8atlAeC-pniBQ&sa=X&oi=book_result&ct=result&resnum=6#v=onepage&q=service%20escalation%20nagios&f=false


On Sun, Oct 4, 2009 at 10:35 PM, Stuart Browne <
stuart.bro...@ausregistry.com.au> wrote:

> > -Original Message-
> > From: Justin Pryzby [mailto:just...@norchemlab.com]
> > Sent: Monday, 5 October 2009 02:50
> > To: nagios-users@lists.sourceforge.net
> > Subject: [Nagios-users] escalation for receiving only recovery events?
> >
> > A coworker wants to receive periodic notifies for failing services,
> > and I want to receive only the first one.  I can implement that using
> > an "inverted" escalation (removing me from the notify list at the 2nd
> > notification).
> >
> > However I *do* want to receive recovery events, even if they're after
> > the 2nd notification.  Is that configuration possible?
>
> Two different contact groups, yourself, and 'everyone else'..
>
> In the base check, put both groups, saying you want the options w,c,r.  In
> the escalation, put just everyone else, with options w,c and
> first_notification of 2+.
>
> Or something like that ;)
>
> Stuart
>
>
> --
> Come build with us! The BlackBerry® Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9-12, 2009. Register now!
> http://p.sf.net/sfu/devconf
> ___
> 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
>



-- 
Cordially,
Shadhin Rahman
--
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference___
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] escalation for receiving only recovery events?

[Stuart Browne]

> -Original Message-
> From: Justin Pryzby [mailto:just...@norchemlab.com] 
> Sent: Monday, 5 October 2009 02:50
> To: nagios-users@lists.sourceforge.net
> Subject: [Nagios-users] escalation for receiving only recovery events?
> 
> A coworker wants to receive periodic notifies for failing services,
> and I want to receive only the first one.  I can implement that using
> an "inverted" escalation (removing me from the notify list at the 2nd
> notification).
> 
> However I *do* want to receive recovery events, even if they're after
> the 2nd notification.  Is that configuration possible?

Two different contact groups, yourself, and 'everyone else'..

In the base check, put both groups, saying you want the options w,c,r.  In the 
escalation, put just everyone else, with options w,c and first_notification of 
2+.

Or something like that ;)

Stuart

--
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
___
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] escalation for receiving only recovery events?

[Justin Pryzby]

A coworker wants to receive periodic notifies for failing services,
and I want to receive only the first one.  I can implement that using
an "inverted" escalation (removing me from the notify list at the 2nd
notification).

However I *do* want to receive recovery events, even if they're after
the 2nd notification.  Is that configuration possible?

Justin

--
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
___
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] Escalation notification time shorter than service check time: bug?

[Kelly Jones]

I did this:

define serviceescalation {
 servicegroup_name really-important-services
 first_notification 1
 last_notification 5
 contact_groups level1-oncall
 notification_interval 5
}

define serviceescalation {
 servicegroup_name really-important-services
 first_notification 6
 last_notification 0
 contact_groups level1-oncall,level2-oncall
 notification_interval 5
}

I wanted level1-oncall notified every 5m for 25m when one of
really-important-services went bad, and then level1-oncall and
level2-oncall notified every 5m after 30m.

However, since my service check interval is 20m, level2-oncall didn't
get notified until 6*20m or 120m later.

Nagios didn't warn me about this when I restarted it.

Is this a known bug? Intended behavior? Did I confuse nagios by using
a servicegroup instead of a single service?

-- 
We're just a Bunch Of Regular Guys, a collective group that's trying
to understand and assimilate technology. We feel that resistance to
new ideas and technology is unwise and ultimately futile.

-
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Register now and save $200. Hurry, offer ends at 11:59 p.m., 
Monday, April 7! Use priority code J8TLD2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
___
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] escalation with groups

[stephen wing]

Hi all

I need to setup escalations, at the minute I have successfully
setup an escalation on a service. What I need to do is to setup escalations
on a host_group. Can anyone let me know what the escalation type is and the
variables that go with it. 

 

Regards

Stephen

 

---

Stephen Wing

Steria Limited

Senior Technical Consultant

Telephone  02890393605

Mobile   07966823605

 


*
This email originates from Steria Limited, registered office: Three Cherry 
Trees Lane, Hemel Hempstead, Hertfordshire HP2 7AH; Registered in England and 
Wales, number 2706218; www.steria.co.uk.
 
This email and any attachments may contain confidential information and may be 
subject to copyright or other intellectual property rights.  It is only for the 
use of the addressee(s). You are prohibited from copying, forwarding, 
disclosing, saving or otherwise using it in any way if you are not the 
addressee(s) or responsible for delivery.
If you receive this email by mistake, please advise the sender and cancel it 
immediately.
Steria may monitor the content of emails within its network to ensure 
compliance with its policies and procedures.
Any email is susceptible to alteration and its integrity cannot be assured. 
Steria shall not be liable if the message is altered, modified, falsified, or 
edited.

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/___
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] escalation

[Richard Mohr]

On Mon, 2007-10-08 at 12:29 -0700, Siwei Zhang wrote:

> I am trying to configure the escalation but never received the
> escalation email.
...
> define service{
...
> max_check_attempts  1
> contact_groups  g1,g2
> normal_check_interval   5
> retry_check_interval5
> process_perf_data   1
> notification_interval   0
...
> }

You have notification_interval set to 0.  According to the
documentation, this means that Nagios will never re-notify contacts
about a problem, so your escalation never goes into effect.

-- 
Rick Mohr
Systems Developer
Ohio Supercomputer Center


-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
___
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] escalation

[hindrek murdsalu]

First, you don't really want to add r to escalation_options as you only
want it to escalate when the status is critical, not when it's critical
and recovery.

Second, it doesn't make much sense as an "escalation" as the
notification interval is supposed to increase when you define your
escalation, you do exactly the opposite, although it probably is not the
cause, you could add a bigger notification_interval to service than to
service escalation.

 

(forgot to change the "To..." address to Nagios-user, now the original
poster gets 2 mails, but oh well) 



From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Siwei
Zhang
Sent: 8. oktoober 2007. a. 22:30
To: nagios-users
Subject: [Nagios-users] escalation

 

Hi there,

 

I am trying to configure the escalation but never received the
escalation email.

What might be wrong? The followings are my configurations.

Thanks.

 

Kevin SZ

 

 

define service{

use generic-service

hostgroup_name  

host_name   

service_description check-host-alive

check_command   check-host-alive

is_volatile 0

check_period24x7

max_check_attempts  1

contact_groups  g1,g2

normal_check_interval   5

retry_check_interval5

process_perf_data   1

notification_interval   0

notification_period 24x7

notification_optionsw,u,c,r

notifications_enabled   1

}

 

 

 

define serviceescalation{

host_name 

service_description check-host-alive

contact_groups g1,g2

first_notification 2

last_notification 0

notification_interval 300

escalation_options c,r

}

 

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/___
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] escalation

[Siwei Zhang]

Hi Valdinger,

 


Thanks for your email. I have set  retain_nonstatus_information0 in
hosts.cfg ans services.cfg

But I still can not receive the escalation email.

 

Kevin SZ

 

 

define service{

namegeneric-service

active_checks_enabled   1

passive_checks_enabled  1

parallelize_check   1

obsess_over_service 1

check_freshness 1

notifications_enabled   1

event_handler_enabled   1

flap_detection_enabled  1

process_perf_data   1

retain_status_information   1

retain_nonstatus_information   0

register  0

}

 

 

 

# Generic host definition template

define host{

namegeneric-host; The name of
this host template - referenced in

notifications_enabled   1   ; Host notifications are
enabled

event_handler_enabled   1   ; Host event handler is
enabled

flap_detection_enabled  1   ; Flap detection is
enabled

process_perf_data   1   ; Process performance
data

retain_status_information   1   ; Retain status
information across program restarts

retain_nonstatus_information0   ; Retain non-status
information across program restarts

notification_optionsd,u,r

register0   ; DONT REGISTER THIS
DEFINITION - ITS NOT A REAL HOST, JU

}

 

 

  _  

From: Valdinger, Stephen (DOV, MSX) [mailto:[EMAIL PROTECTED] 
Sent: Monday, October 08, 2007 12:40 PM
To: Siwei Zhang
Cc: nagios-users@lists.sourceforge.net
Subject: RE: [Nagios-users] escalation

 

Have a look at the section on “retention notes” in this documentation
link. It may be exactly what you are looking for

 

http://nagios.sourceforge.net/docs/3_0/objectdefinitions.html#retention_
notes

 

-hth

 

Stephen

 

  _  

From: Siwei Zhang [mailto:[EMAIL PROTECTED] 
Sent: Monday, October 08, 2007 3:30 PM
To: nagios-users
Subject: [Nagios-users] escalation

 

Hi there,

 

I am trying to configure the escalation but never received the
escalation email.

What might be wrong? The followings are my configurations.

Thanks.

 

Kevin SZ

 

 

define service{

use generic-service

hostgroup_name  

host_name   

service_description check-host-alive

check_command   check-host-alive

is_volatile 0

check_period24x7

max_check_attempts  1

contact_groups  g1,g2

normal_check_interval   5

retry_check_interval5

process_perf_data   1

notification_interval   0

notification_period 24x7

notification_optionsw,u,c,r

notifications_enabled   1

}

 

 

 

define serviceescalation{

host_name 

service_description check-host-alive

contact_groups g1,g2

first_notification 2

last_notification 0

notification_interval 300

escalation_options c,r

}

 


-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/___
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] escalation

[Siwei Zhang]

Hi there,

 

I am trying to configure the escalation but never received the
escalation email.

What might be wrong? The followings are my configurations.

Thanks.

 

Kevin SZ

 

 

define service{

use generic-service

hostgroup_name  

host_name   

service_description check-host-alive

check_command   check-host-alive

is_volatile 0

check_period24x7

max_check_attempts  1

contact_groups  g1,g2

normal_check_interval   5

retry_check_interval5

process_perf_data   1

notification_interval   0

notification_period 24x7

notification_optionsw,u,c,r

notifications_enabled   1

}

 

 

 

define serviceescalation{

host_name 

service_description check-host-alive

contact_groups g1,g2

first_notification 2

last_notification 0

notification_interval 300

escalation_options c,r

}

 


-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/___
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] Escalation notifications

[Hugo van der Kooij]

On Sun, 28 Jan 2007, 3ala2 M. Shakhshir wrote:

> Am having a 2.6 Nagios, I want it to send only an email to contacts when a
> host  or service goes down, and send an SMS to the same contacts after an
> hour, how this could be implemented in escalations?

Perhaps you can indicate which part of the manuals you did read and which 
parts you did not understand? Because this information can be obtained by 
reading the manual carefully. So if there is a specific issue not clear in 
the regular notifications or the escalation notification please provide 
more details on what you tried.

If you need very generic help. Try your favorite search engine and look 
around for examples. They pass the list every now and againdso there must 
be plenty avaiable online some of which may fit your needs.

Hugo.

-- 
[EMAIL PROTECTED]   http://hvdkooij.xs4all.nl/
This message is using 100% recycled electrons.

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
___
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] Escalation notifications

[3ala2 M. Shakhshir]

Greetings,

Am having a 2.6 Nagios, I want it to send only an email to contacts when a
host  or service goes down, and send an SMS to the same contacts after an
hour, how this could be implemented in escalations?

 

Best Regards,

Ala' Shakhshir

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV___
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] escalation/notification question

[Jeff Williams]

Do I have to explicitly say in the escalations that warnings should stop at 1 notification, rather than just say only critical and recovery can go from 2 to 5 like I had before? Do I have to put something like this?
define serviceescalation{
   
host_name
viper
   
service_description  
DISK /
   
first_notification    1
   
last_notification 1
   
notification_interval 0 
   
contact_groups   
admins
   
escalation_options    w
}On 8/23/06, Michael Koprowski <
[EMAIL PROTECTED]> wrote:
















I may be wrong, but my interpretation is you
will receive a warning, unknown, critical, and recovery alerts if these changes
are reported on viper's disk and will notify you every 5 minutes.

 





If I have a host called viper with the following definitions, I'm
wondering why the group admins gets warning notifications for the service
"DISK /" after the first notification. To me, these definitions say
that admins should get no more than 5 notifications and no warning
notifications after the first one. Am I wrong in thinking that? In testing
this, the admins group got at least 8 warning notifications. 











host definition
define host{
   
use  
generic-host
   
host_name
viper
   
alias
viper
   
address  
127.0.0.1
   
parents  
localhost
   
check_command
check-host-alive
   
notification_interval 0
   
notification_options  d,r
   
notification_period   never 
   
contact_groups   
admins
}

service definition
define service{
   
use  
generic-service
   
host_name
viper
   
service_description  
DISK / 
   
is_volatile  
0
   
check_period 
24x7
   
retry_check_interval  1
   
contact_groups   
admins
   
notification_interval 5 
   
notification_period  
24x7
   
notification_options 
w,u,c,r
   
check_command
check_nrpe!check_disk1
}
escalation definition
define serviceescalation{ 
   
host_name
viper
   
service_description  
DISK /
   
first_notification   
2
   
last_notification
2
    notification_interval
5 
   
contact_groups   
admins
   
escalation_options   
c,r
}

define serviceescalation{
   
host_name
viper
   
service_description  
DISK / 
    first_notification   
3
   
last_notification
4
   
notification_interval 5
   
contact_groups   
admins
   
escalation_options   
c,r 
}
define serviceescalation{
   
host_name
viper
   
service_description  
DISK /
   
first_notification   
5
   
last_notification
0
   
notification_interval 0 
   
contact_groups   
admins
   
escalation_options   
c,r
}
















Contactgroup:
define contactgroup{
   
contactgroup_name   admins
   
alias  
Nagios Administrators
   
members
nagios
    }
 
 











   Contacts:








define contact{
   
contact_name   
nagios
   
alias  
Nagios Admin
   
service_notification_period 24x7
   
host_notification_period    24x7 
   
service_notification_options    w,u,c,r
   
host_notification_options   d,r
    service_notification_commands  
notify-by-email
   
host_notification_commands  host-notify-by-email 
   
email  
[EMAIL PROTECTED]
    }





The group "admins" should get warnings, but since the
escalation file says only go past original notification for critical and
recovery, shouldn't I just get 1 warning notification or 2 at most? 








Also, here are the generic-host and generic-service definitions. I forgot to
include those before as well.
define host{
   
name   
generic-host    ; The name of this host template 
   
check_interval 
0
   
max_check_attempts 
2
   
notifications_enabled  
1   ; Host notifications are enabled
   
event_handler_enabled  
1   ; Host event handler is enabled 
   
flap_detection_enabled 
1   ; Flap detection is enabled
   
failure_prediction_enabled 
1   ; Failure prediction is enabled
   
process_perf_data  
1   ; Process performance data 
   
retain_status_information  
1   ; Retain status information across
program restarts
   
retain_nonstatus_information   
1   ; Retain non

Re: [Nagios-users] escalation/notification question

[Jeff Williams]

If I have a host called viper with the following definitions, I'm wondering why the group admins gets warning notifications for the service "DISK /" after the first notification. To me, these definitions say that admins should get no more than 5 notifications and no warning notifications after the first one. Am I wrong in thinking that? In testing this, the admins group got at least 8 warning notifications.

host definitiondefine host{    use   generic-host    host_name viper    alias viper    address   

127.0.0.1    parents   localhost    check_command check-host-alive    notification_interval 0    notification_options  d,r    notification_period   never
    contact_groups    admins}service definitiondefine service{    use   generic-service    host_name viper    service_description   DISK /
    is_volatile   0    check_period  24x7    retry_check_interval  1    contact_groups    admins    notification_interval 5
    notification_period   24x7    notification_options  w,u,c,r    check_command check_nrpe!check_disk1}escalation definitiondefine serviceescalation{
    host_name viper    service_description   DISK /    first_notification    2    last_notification 2    notification_interval 5
    contact_groups    admins    escalation_options    c,r}define serviceescalation{    host_name viper    service_description   DISK /
    first_notification    3    last_notification 4    notification_interval 5    contact_groups    admins    escalation_options    c,r
}define serviceescalation{    host_name viper    service_description   DISK /    first_notification    5    last_notification 0    notification_interval 0
    contact_groups    admins    escalation_options    c,r}
Contactgroup:define contactgroup{    contactgroup_name   admins    alias   Nagios Administrators    members nagios    }
    Contacts:
define contact{    contact_name    nagios    alias   Nagios Admin    service_notification_period 24x7    host_notification_period    24x7
    service_notification_options    w,u,c,r    host_notification_options   d,r    service_notification_commands   notify-by-email    host_notification_commands  host-notify-by-email
    email   [EMAIL PROTECTED]    }The group "admins" should get warnings, but since the escalation file says only go past original notification for critical and recovery, shouldn't I just get 1 warning notification or 2 at most?
Also, here are the generic-host and generic-service definitions. I forgot to include those before as well.define host{    name    generic-host    ; The name of this host template
    check_interval  0    max_check_attempts  2    notifications_enabled   1   ; Host notifications are enabled    event_handler_enabled   1   ; Host event handler is enabled
    flap_detection_enabled  1   ; Flap detection is enabled    failure_prediction_enabled  1   ; Failure prediction is enabled    process_perf_data   1   ; Process performance data
    retain_status_information   1   ; Retain status information across program restarts    retain_nonstatus_information    1   ; Retain non-status information across program restarts    register    0   ; DONT REGISTER THIS DEFINITION - ITS NOT A REAL HOST, JUST A TEMPLATE!
    } define service{    name    generic-service ; The 'name' of this service template    max_check_attempts  2    normal_check_interval   5
    active_checks_enabled   1   ; Active service checks are enabled    passive_checks_enabled  1   ; Passive service checks are enabled/accepted    parallelize_check   1   ; Active service checks should be parallelized (disabling this can lead to major performance problems)
    obsess_over_service 1   ; We should obsess over this service (if necessary)    check_freshness 0   ; Default is to NOT check service 'freshness'    notifications_enabled   1   ; Service notifications 

Re: [Nagios-users] escalation/notification question

[Jeff Williams]

If I have a host called viper with the following definitions, I'm wondering why the group admins gets warning notifications for the service "DISK /" after the first notification. To me, these definitions say that admins should get no more than 5 notifications and no warning notifications after the first one. Am I wrong in thinking that? In testing this, the admins group got at least 8 warning notifications.
host definition---define host{    use   generic-host    host_name viper    alias viper    address   

127.0.0.1    parents   localhost    check_command check-host-alive    notification_interval 0    notification_options  d,r    notification_period   never
    contact_groups    admins}service definition---define service{    use   generic-service    host_name viper    service_description   DISK /
    is_volatile   0    check_period  24x7    retry_check_interval  1    contact_groups    admins    notification_interval 5
    notification_period   24x7    notification_options  w,u,c,r    check_command check_nrpe!check_disk1}escalation definition---define serviceescalation{
    host_name viper    service_description   DISK /    first_notification    2    last_notification 2    notification_interval 5
    contact_groups    admins    escalation_options    c,r}define serviceescalation{    host_name viper    service_description   DISK /
    first_notification    3    last_notification 4    notification_interval 5    contact_groups    admins    escalation_options    c,r
}define serviceescalation{    host_name viper    service_description   DISK /    first_notification    5    last_notification 0    notification_interval 0
    contact_groups    admins    escalation_options    c,r}Please let me know if more info is needed. Thanks in advance.Jeff

Umm can we see your contacts and contactgroup configs? Bet admins get warnings thereToryHere they are. Everything is intact from how I have it on the server except for the email address.
Contactgroup:define contactgroup{    contactgroup_name   admins    alias   Nagios Administrators    members nagios    }Contacts:
define contact{    contact_name    nagios    alias   Nagios Admin    service_notification_period 24x7    host_notification_period    24x7
    service_notification_options    w,u,c,r    host_notification_options   d,r    service_notification_commands   notify-by-email    host_notification_commands  host-notify-by-email
    email   [EMAIL PROTECTED]    }Yes admins should get warnings, but since the escalation file says only go past original notification for critical and recovery, shouldn't I just get 1 warning notification or 2 at most?

-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&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

Re: [Nagios-users] escalation/notification question

[Tory M Blue]

On 8/18/06, Jeff Williams <[EMAIL PROTECTED]> wrote:
If I have a host called viper with the following definitions, I'm wondering why the group admins gets warning notifications for the service "DISK /" after the first notification. To me, these definitions say that admins should get no more than 5 notifications and no warning notifications after the first one. Am I wrong in thinking that? In testing this, the admins group got at least 8 warning notifications.
host definition---define host{    use   generic-host    host_name viper    alias viper    address   

127.0.0.1    parents   localhost    check_command check-host-alive    notification_interval 0    notification_options  d,r    notification_period   never
    contact_groups    admins}service definition---define service{    use   generic-service    host_name viper    service_description   DISK /
    is_volatile   0    check_period  24x7    retry_check_interval  1    contact_groups    admins    notification_interval 5
    notification_period   24x7    notification_options  w,u,c,r    check_command check_nrpe!check_disk1}escalation definition---define serviceescalation{
    host_name viper    service_description   DISK /    first_notification    2    last_notification 2    notification_interval 5
    contact_groups    admins    escalation_options    c,r}define serviceescalation{    host_name viper    service_description   DISK /
    first_notification    3    last_notification 4    notification_interval 5    contact_groups    admins    escalation_options    c,r
}define serviceescalation{    host_name viper    service_description   DISK /    first_notification    5    last_notification 0    notification_interval 0
    contact_groups    admins    escalation_options    c,r}Please let me know if more info is needed. Thanks in advance.Jeff

Umm can we see your contacts and contactgroup configs? Bet admins get warnings thereTory
-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&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

[Nagios-users] escalation/notification question

[Jeff Williams]

If I have a host called viper with the following definitions, I'm wondering why the group admins gets warning notifications for the service "DISK /" after the first notification. To me, these definitions say that admins should get no more than 5 notifications and no warning notifications after the first one. Am I wrong in thinking that? In testing this, the admins group got at least 8 warning notifications.
host definition---define host{    use   generic-host    host_name viper    alias viper    address   
127.0.0.1    parents   localhost    check_command check-host-alive    notification_interval 0    notification_options  d,r    notification_period   never
    contact_groups    admins}service definition---define service{    use   generic-service    host_name viper    service_description   DISK /
    is_volatile   0    check_period  24x7    retry_check_interval  1    contact_groups    admins    notification_interval 5
    notification_period   24x7    notification_options  w,u,c,r    check_command check_nrpe!check_disk1}escalation definition---define serviceescalation{
    host_name viper    service_description   DISK /    first_notification    2    last_notification 2    notification_interval 5
    contact_groups    admins    escalation_options    c,r}define serviceescalation{    host_name viper    service_description   DISK /
    first_notification    3    last_notification 4    notification_interval 5    contact_groups    admins    escalation_options    c,r
}define serviceescalation{    host_name viper    service_description   DISK /    first_notification    5    last_notification 0    notification_interval 0
    contact_groups    admins    escalation_options    c,r}Please let me know if more info is needed. Thanks in advance.Jeff
-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&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

[Nagios-users] Escalation best practices

[Justin Shore]

I've just started rolling out escalations at one of my sites using
Nagios.  I'm not a big escalation buff though.  I have a question that I
couldn't answer via that docs.

Is there any other way of matching up a serviceescalation definition
with a service definition other than the service_description value?  I
use that field for a verbose description of my services (not just SMTP,
HTTP, etc).  For example I use check_snmp_int to check the state of a
serial interface on a router.  The service_description field includes
the circuit provider's name, circuit ID, support telephone #, and a
description of the circuit.  All that text is what's used to match the
serviceescalation definition to the service definition.  I don't know
what else we could match on but I'm hopeful that there's something else.

Many thanks
  Justin

--
Justin Shore, Network Engineer
SKT Business Communication Solutions
Office:  (316) 265-9555 x3217 




---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642
___
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] escalation procedures?

[Tom Cruickshank]

I seem to need a visit to the eye doctor.Apparnantly my eye sight is just not what it used to be. Now if only I could remove my original email from the mailing list :PTom
On 3/9/06, Werner Flamme <[EMAIL PROTECTED]> wrote:
-BEGIN PGP SIGNED MESSAGE-Hash: SHA1Tom Cruickshank schrieb am 09.03.2006 15:56:> Hello,>I was wondering if it was possible to configure Nagios in a way that> if it detects something going down or unreachable, it sends an email to one
> person, but if it detects it again on the 2nd time, it sends an email to a> different person? Kind of like escalation procedures.>> I tried looking in the manual but could not find anything of that nature.
>> Would anyone happen to know?>> Thanks for any assistance.>> Tom Cruickshank>Tom,are you kidding? ;-)Search the mailing list archive for "escalation" or "service escalation",
you will find a lot about it. And maybe you read even where to look in themanual ;-)For Release 2.0, look at http://nagios.sourceforge.net/docs/2_0/toc.html
.You will find "Notification escalations" under the heading "AdvancedTopics". And when you want the documentation of Version 1.x, just change/2_0/ to /1_0/ in the URL.Took me 3 minutes to find out.
HTH,Werner- --Werner Flamme, Abt. WKDVUFZ Umweltforschungszentrum Leipzig-Halle GmbH,Permoserstr. 15 - 04318 LeipzigTel.: (0341) 235-3921 - Fax (0341) 235-453921
http://www.ufz.de - eMail: [EMAIL PROTECTED]-BEGIN PGP SIGNATURE-Version: GnuPG v1.4.2 (GNU/Linux)Comment: Using GnuPG with Mozilla - 
http://enigmail.mozdev.orgiD8DBQFEEEuSk33Krq8b42MRArsCAJ9N9op1X/IHFjS0JTAtNWedSd/XdQCffmn5QtzJ+Uc2ERFtN1EmtIFqn20==gmUl-END PGP SIGNATURE
This SF.Net email is sponsored by xPML, a groundbreaking scripting languagethat extends applications into web and mobile media. Attend the live webcastand join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642___
Nagios-users mailing listNagios-users@lists.sourceforge.nethttps://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] escalation procedures?

[Werner Flamme]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Tom Cruickshank schrieb am 09.03.2006 15:56:
> Hello,
>I was wondering if it was possible to configure Nagios in a way that
> if it detects something going down or unreachable, it sends an email to one
> person, but if it detects it again on the 2nd time, it sends an email to a
> different person? Kind of like escalation procedures.
> 
> I tried looking in the manual but could not find anything of that nature.
> 
> Would anyone happen to know?
> 
> Thanks for any assistance.
> 
> Tom Cruickshank
> 
Tom,

are you kidding? ;-)

Search the mailing list archive for "escalation" or "service escalation",
you will find a lot about it. And maybe you read even where to look in the
manual ;-)

For Release 2.0, look at http://nagios.sourceforge.net/docs/2_0/toc.html.
You will find "Notification escalations" under the heading "Advanced
Topics". And when you want the documentation of Version 1.x, just change
/2_0/ to /1_0/ in the URL.

Took me 3 minutes to find out.

HTH,
Werner

- --
Werner Flamme, Abt. WKDV
UFZ Umweltforschungszentrum Leipzig-Halle GmbH,
Permoserstr. 15 - 04318 Leipzig
Tel.: (0341) 235-3921 - Fax (0341) 235-453921
http://www.ufz.de - eMail: [EMAIL PROTECTED]




-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEEEuSk33Krq8b42MRArsCAJ9N9op1X/IHFjS0JTAtNWedSd/XdQCffmn5
QtzJ+Uc2ERFtN1EmtIFqn20=
=gmUl
-END PGP SIGNATURE-


---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&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

[Nagios-users] escalation procedures?

[Tom Cruickshank]

Hello,     I was wondering if it was possible to configure Nagios in a way that if it detects something going down or unreachable, it sends an email to one person, but if it detects it again on the 2nd time, it sends an email to a different person? Kind of like escalation procedures.
I tried looking in the manual but could not find anything of that nature.Would anyone happen to know?Thanks for any assistance.Tom Cruickshank

[Nagios-users] Escalation questions

[Justin Shore]

Greetings.  I'm trying to set up a quick escalation procedure for 3
hosts.  Host Down alerts are generated for these hosts on a daily basis
due to the load on the first of the 3 items.  This particular problem
always resolves itself by the time next check happens (causing a host
down alert followed by a host up alert 2 minutes later).

What I'd like to do is use an escalation procedure with the first
contact being the user "null" I created on my Nagios box for the
explicit purpose of directing mail to /dev/null (this works already with
a few other contacts).  I've already created a "null" contactgroup for
this purpose.  I'd like the normal alerting process to start again after
15 minutes if the host(s) is still down.  This would prevent half a
dozen people from being paged daily with what equates to a bogus alert
(causing them to slowly but surely stop paying as much attention to the
alerts over time).  I'm a bit confused on how to implement this though.
Here's what I've got so far:

define hostescalation{
host_name   cmts-1.clr
contact_groups  isp-net-admins,cmts-admins
first_notification  1
notification_interval   15
escalation_period   24x7
escalation_options  d,u,r
}

isp-net-admins and cmts-admins are the normal contactgroups for these
hosts.  "null" is the contact(group) I want to use for the first 15
minutes before the escalation takes place on these 3 hosts.  I'm a
little confused on the notification_interval options.  My hosts/services
are by default running at 180 (minutes).  Will the notification_interval
in this hostescalation definition override that?  I'm not sure if I'm
taking the right approach to this or not so I welcome any and all
suggestions.

I've been reviewing the online docs and have made good headway.  I'm
stuck at the moment though.

Thanks 
  Justin

--
Justin Shore, Network Engineer
SKT Business Communication Solutions
Office:  (316) 265-9555 x3217 




---
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://ads.osdn.com/?ad_idv37&alloc_id865&op=click
___
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] escalation groups?

[Guy Knights]

I'm currently configuring an install of Nagios 1.2 to provide server 
monitoring for my workplace. I have the hosts, hostgroups, contacts, 
services, etc set up and working fine.


I've tested escalations and they're working fine, but I'm trying to work 
out how I can set up our proposed notification schedule. Below is a 
brief outline of what we have already:


   * Multiple hosts in 3 different host groups
   * Multiple contacts, in 3 different contact groups
   * About 30 different services, based on two different templates, a
 medium priority template and a high priority template
   * Two different time periods, one for standard working hours, and
 one for weekend on-call hours

Is it possible to set up something like a "group" of escalations, so 
certain services follow one escalation pattern, another set of services 
follows another escalation pattern, etc? The problem is that because we 
have so many services already, and the notifications for these services 
are based on templates, it looks to me like we'd have to set up a huge 
amount of escalations to accomplish the escalation schedule we're aiming 
for.


Basically, we would just like to be able to choose the set of 
escalations used, based upon which template the service uses. Is this 
possible?


I apologise if this is confusing to follow, I'm happy to elaborate if 
people aren't sure what I'm on about!


Regards,
Guy

-
Guy Knights
Computer Systems Officer
Queensland University of Technology
Victoria Park Road
Kelvin Grove
QLD
Ph: (07) 3864 3350
Email: [EMAIL PROTECTED]






---
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://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
___
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] Escalation Question

[Mark Ahlstrom]

I inherited a nagios system w/ wild-carded escalations for services and
hosts. This has helped us manage a nightmare: 300 hosts, 4000 services
and 16,000 escalations. 

I can bring other groups into the mix by making them the primary
contacts of the service. But my group will be brought into the pages
when they don't answer them. Does anyone know of a good way I could
remove my group from the pages all the while maintaining my
administrative sanity? 

Here are my service escalations... 

define serviceescalation{
host_name   *
service_description *
first_notification  2
last_notification   0
contact_groups  oncall
notification_interval   10
}

define serviceescalation{
host_name   *
service_description *
first_notification  3
last_notification   0
contact_groups  backup
notification_interval   10
}

define serviceescalation{
host_name   *
service_description *
first_notification  4
last_notification   0
contact_groups  tertiary
notification_interval   10
}

define serviceescalation{
host_name   *
service_description *
first_notification  5
last_notification   0
contact_groups  admins
notification_interval   10
}

Mark



---
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://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
___
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