[Nagios-users] service escalations
Hi - can someone confirm if the following scenario regards service
escalations is correct?
I have a service check that simply performs a TCP check, if it fails it
will email the contact with a defined notification_interval of 5mins.
I also have a serviceescalation defined as follows:
define serviceescalation{
hostgroup_name desktopsnahisservers
service_description DESKTOP SNA SERVICE TCP 4097
first_notification 3
last_notification 0
notification_interval 5
contactsme_at_home
}
If the TCP check continues to fail the service escalation contact starts
to get alerts but the actual contact for the defined service doesn't.
Is this behaviour to be expected?
As a solution I've simply added the defined service contact to also be a
contact under the serviceescalation section as well.
I'm running Nagios 3.4.3.
Thanks - Julian.
Julian Grunnell | Unix Analyst, Infrastructure | TD Direct Investing
T: +44 (0) 113 346 2824 | M: +44 (0) 7889 352527
---
Consider the environment: Please don't print this e-mail unless you really need
to.
Confidentiality: This email and its attachments are intended for the above
named only and may be confidential. If they have come to you in error you must
take no action based on them, nor must you copy or show them to anyone; please
reply to this email and highlight the error.
Viruses: Although we have taken steps to ensure that this email and
attachments are free from any virus, we advise that in keeping with good
computing practice the recipient should ensure that they are actually
virus-free.
Brokerage services provided by TD Direct Investing (Europe) Limited (a
subsidiary of The Toronto-Dominion Bank). Authorised and regulated by the
Financial Services Authority (FSA registered number 141282), member of the
London Stock Exchange and the PLUS market. Incorporated in England and Wales
under registration number 2101863. Registered office: Exchange Court, Duncombe
Street, Leeds LS1 4AX. Banking services provided by TD Bank N.V. authorised and
regulated by De Nederlandsche Bank and the Financial Services Authority for UK
Business (FSA registered number 216791). Incorporated in the Netherlands and
registered as a branch in England and Wales under branch registration number
BR006780.
--
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
MVPs and experts. SALE $99.99 this month only -- learn more at:
http://p.sf.net/sfu/learnmore_122412___
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] service escalations
On 14/01/13 14:41, julian_grunn...@tdwh.co.uk wrote:
Hi - can someone confirm if the following scenario regards service
escalations is correct?
I have a service check that simply performs a TCP check, if it fails
it will email the contact with a defined notification_interval of 5mins.
I also have a serviceescalation defined as follows:
define serviceescalation{
hostgroup_name desktopsnahisservers
service_description DESKTOP SNA SERVICE TCP 4097
first_notification 3
last_notification 0
notification_interval 5
contactsme_at_home
}
If the TCP check continues to fail the service escalation contact
starts to get alerts but the actual contact for the defined service
doesn't.
Is this behaviour to be expected?
As a solution I've simply added the defined service contact to also be
a contact under the serviceescalation section as well.
I'm running Nagios 3.4.3.
Thanks - Julian.
Julian Grunnell | Unix Analyst, Infrastructure | TD Direct Investing
T: +44 (0) 113 346 2824 | M: +44 (0) 7889 352527
Escalations are added and expand the capability of notifications , when
the escalation logics is activated the normal notification logic is
suspended and the escalation is the way nagios is processing the alerts.
So if after the 3rd alert only the escalation alert is received - then
the logic is working as it should .
Assaf
--
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
MVPs and experts. SALE $99.99 this month only -- learn more at:
http://p.sf.net/sfu/learnmore_122412___
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] service escalations
On 1/14/2013 9:41 AM, julian_grunn...@tdwh.co.uk wrote: If the TCP check continues to fail the service escalation contact starts to get alerts but the actual contact for the defined service doesn't. Try changing contacts me_at_home to contacts +me_at_home. -- -Chris Nothing in this message is intended to make or accept an offer or to form a contract, except that an attachment that is an image of a contract bearing the signature of an officer of our company may be or become a contract. This message (including any attachments) is intended only for the use of the individual or entity to whom it is addressed. It may contain information that is non-public, proprietary, privileged, confidential, and exempt from disclosure under applicable law or may constitute as attorney work product. If you are not the intended recipient, we hereby notify you that any use, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this message in error, please notify us immediately by telephone and delete this message immediately. Thank you. -- Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. SALE $99.99 this month only -- learn more at: http://p.sf.net/sfu/learnmore_122412 ___ 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] Service escalations without contacts or groups defined on the services themselves
Kevin Kenny wrote: I find this a convenient configuration because it means I don't have to explicitly define contacts or contact groups at either the service template or service check itself and makes management somewhat simpler. Well, that's one way to do it, but... Despite the warnings, and even though this configuration works just fine, is it recommended? ...I can't recommend it, personally. It may work for you now, but it won't scale up. I have over a thousand hosts and ten thousand services. My preflight check has to be clean, or I would miss one new configuration warning as ten thousand preventable warnings scrolled past. -- -Chris -- Nothing in this message is intended to make or accept an offer or to form a contract, except that an attachment that is an image of a contract bearing the signature of an officer of our company may be or become a contract. This message (including any attachments) is intended only for the use of the individual or entity to whom it is addressed. It may contain information that is non-public, proprietary, privileged, confidential, and exempt from disclosure under applicable law or may constitute as attorney work product. If you are not the intended recipient, we hereby notify you that any use, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this message in error, please notify us immediately by telephone and delete this message immediately. Thank you. -- All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 ___ 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] Service escalations without contacts or groups defined on the services themselves
All of my service checks are based on templates where notifications are
enabled, the notification period set to 24x7, notification type is set to
U,C etc. But there are no contacts or contact groups associated in the
service check templates.
When I add a new service check, the check is always based on one of these
templates. However I *still don't* add any contacts or groups to the actual
checks themselves.
The service checks all get added to to a service group called
Critical-Services.
I also have a number of users who are members of a contact group called
Duty-Admin-Pagers.
I have a service escalation configured with a linked contact group of
Duty-Admin-Pagers (above) and with a servicegroup_name of Critical-Services,
it looks like this:
define serviceescalation{
servicegroup_name Critical-Services
contact_groups Duty-Admin
contacts
first_notification 1
last_notification 999
notification_interval 1
escalation_period 24x7
escalation_options u,c
}
Whenever a service goes CRITICAL HARD and exceeds the number of retries I
get pager alerts fired off just as I expect.
However when I load this configuration into Nagios I get warnings such as:
Warning Service 'APC-Power-Output' on host 'APC-PDU-0299' has no default
contacts or contactgroups defined!
The escalation and notifications still work and still send notifications to
the contact_group Duty-Admin defined in the service escalation.
I find this a convenient configuration because it means I don't have to
explicitly define contacts or contact groups at either the service template
or service check itself and makes management somewhat simpler.
Despite the warnings, and even though this configuration works just fine, is
it recommended?
Thanks
Kevin
--
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2___
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] Service escalations registering, but not enforcing
On May 13, 2009, at 5:43 PM, Bruce Thayre wrote: So i've also tested this problem with host escalations, and i have seen the same behavior. Despite whatever settings i put into my host escalations, or my host definitions, i'm still receiving notifications every 30 minutes, any ideas? Did you change interval_length in nagios.cfg to be 0.5? Do you see the expected value for notification_interval in objects.cache? Do you have multiple nagios daemons running at the same time? -- Marc -- The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your production scanning environment may not be a perfect world - but thanks to Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-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] Service escalations registering, but not enforcing
Hello, I'm having an issue i have not been able to resolve. I'm using nagios 3.0.4 and have a ton of service escalations defined, however they do not seem to be enforced. I've also noticed, that while i've defined all of my services to use the generic-service template (which by default, has a notification_interval set to 60) i receive notifications every 30 minutes despite the generic-service definition and escalations. My services.cfg: http://dpaste.com/43794/ My templates.cfg: http://dpaste.com/43795/ If i run nagios -v nagios.cfg my output looks like: Nagios 3.0.4 Copyright (c) 1999-2008 Ethan Galstad (http://www.nagios.org) Last Modified: 10-15-2008 License: GPL Reading configuration data... Running pre-flight check on configuration data... Checking services... Checked 338 services. Checking hosts... Checked 112 hosts. Checking host groups... Checked 5 host groups. Checking service groups... Checked 0 service groups. Checking contacts... Checked 1 contacts. Checking contact groups... Checked 1 contact groups. Checking service escalations... Checked 973 service escalations. Checking service dependencies... Checked 0 service dependencies. Checking host escalations... Checked 0 host escalations. Checking host dependencies... Checked 0 host dependencies. Checking commands... Checked 25 commands. Checking time periods... Checked 5 time periods. Checking for circular paths between hosts... Checking for circular host and service dependencies... Checking global event handlers... Checking obsessive compulsive processor commands... Checking misc settings... Total Warnings: 0 Total Errors: 0 Things look okay - No serious problems were detected during the pre-flight check So nagios can clearly see my service escalations. So is there any apparent reason why my service escalations are not enforced? And also, is there any apparent reason why my notification_interval is enforced as 30 minutes, when it is set to 60 in templates.cfg? Any help/input/ridicule would be greatly appreciated, as if i don't come up with a solution, i'm just going to trash this install and use nagios 2.x Thanks, Bruce -- The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your production scanning environment may not be a perfect world - but thanks to Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-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] Service escalations registering, but not enforcing
So i've also tested this problem with host escalations, and i have seen the same behavior. Despite whatever settings i put into my host escalations, or my host definitions, i'm still receiving notifications every 30 minutes, any ideas? -- The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your production scanning environment may not be a perfect world - but thanks to Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-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] Service Escalations
Ok, I¹ve manage to thoroughly confuse my self with service escalations.
Here is an example of my configs:
--service_definitation:
define service{
use generic-service
host_name box1,box2
service_description disk_space
check_command check_nrpe!check_disks
contact_groups
oncall,developers,backup,tech-team,management
notifications_enabled 1
}
My escalations config:
define serviceescalation{
host_name box1,box2
service_descriptiondisk_space
first_notification 1
last_notification 10
notification_interval 4
contact_groupsoncall
}
define serviceescalation{
host_namebox1,box2
service_description disk_space
first_notification 11
last_notification 20
notification_interval 4
contact_groups oncall,backup
}
define serviceescalation{
host_name box1,box2
service_description disk_space
first_notification21
last_notification 30
notification_interval 4
contact_groups oncall,backup,tech-team
}
define serviceescalation{
host_name box1,box2
service_description disk_space
first_notification 31
last_notification
notification_interval 4
contact_groups oncall,backup,tech-team,management
}
My first question:
There have been two times in the past 24 hours when a service went down, and
within a minute was acknowledged, and everybody got the acknowledgement, not
just the oncall person.
And secondly, if I added and everyone¹ to my service contact_groups¹, and
utilized the time_period option in the escalations config for after hours,
would everyone get the notification during the day?
Thanks!
Robert
-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100url=/___
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] Service Escalations
On Thu, 04 Sep 2008 14:26:04 -0500, Robert Small [EMAIL PROTECTED]
wrote:
Ok, I¹ve manage to thoroughly confuse my self with service escalations.
Here is an example of my configs:
--service_definitation:
define service{
use generic-service
host_name box1,box2
service_description disk_space
check_command check_nrpe!check_disks
contact_groups
oncall,developers,backup,tech-team,management
notifications_enabled 1
}
My escalations config:
define serviceescalation{
[..]
contact_groupsoncall
}
define serviceescalation{
[..]
contact_groups oncall,backup
}
define serviceescalation{
[..]
contact_groups oncall,backup,tech-team
}
define serviceescalation{
[..]
contact_groups oncall,backup,tech-team,management
}
My first question:
There have been two times in the past 24 hours when a service went down, and
within a minute was acknowledged, and everybody got the acknowledgement, not
just the oncall person.
I'm a little confused as to why you have everybody in the service
definition, and then break it down in the escallations. It seems a
slightly unusual way of doing it, but based on the verbiage from the
docs, should work...
http://nagios.sourceforge.net/docs/3_0/escalations.html
The way the docs have it laid out, and using your samples, it'd have
the contact_groups for the service as just oncall. Then for the first
service escallation, which would be from 11, to 20 (not 1 to 10), the
groups would be oncall, and backup. Then on the 21-30, it'd be oncall,
backup, and tech-team, etc etc etc.
And secondly, if I added and everyone¹ to my service contact_groups¹, and
utilized the time_period option in the escalations config for after hours,
would everyone get the notification during the day?
It doesn't seem to mention it that way, but yes, it'd appear to behave
that way.
--
Jon Angliss
-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100url=/
___
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
