Alert Precedence

[Claudio Kuenzler]

Oops, didn't see your second answer where you said you found it. Sorry.

On Sun, Apr 28, 2013 at 12:20 PM, Claudio Kuenzler
<ck at claudiokuenzler.com>wrote:

> Please paste the config of the host and the service from which you
> received the notification (in UI -> show config).
> Also show the relevant entries of the Nagios event log.
>
> On Thu, Apr 25, 2013 at 5:50 PM, Net Warrior <netwarrior863 at gmail.com>wrote:
>
>> Hi
>> I reviewed my alerts and increased the service check interval as this:
>>
>> this is the service
>>
>> notifications_enabled           1
>>         notification_options            w,c
>>         notification_period             24x7
>>         check_period                    24x7
>>         check_interval                  10
>>         max_check_attempts              3
>>         first_notification_delay        0
>>         notification_interval           15
>>
>> This is the host:
>>
>>         check_interval                  1
>>         check_period                    24x7
>>         notification_period             24x7
>>         max_check_attempts              3
>>         notification_interval           10
>>         flap_detection_enabled          0
>>         first_notification_delay        0
>>
>>
>> So, the host is checked every one minute and on the third failure the
>> alert gets fired, for the service I increased it to check every 10 minutes,
>> so in theory the hosts check happens firts withing 3 minutes, as the
>> service is checked every 10 I should not get any alert on them, but I still
>> get the service notifications after the hosts is down.
>>
>> Any help appreciated.
>> Thanks for your time and support.
>>
>>
>> 2013/4/8 Claudio Kuenzler <ck at claudiokuenzler.com>
>>
>>> This is a "basic dependency" in Nagios. When the host is down (hard)
>>> then you won't receive any alerts for the services defined in this host.
>>> What is likely in your case, is that you have scheduled the service
>>> checks more often or faster to alert before the host check. This will
>>> result in some alerts of services before the actual host down alert comes.
>>> You should check out the event log to determine which checks happened
>>> faster to become a hard critical state.
>>>
>>>
>>> On Mon, Apr 8, 2013 at 5:43 PM, Net Warrior <netwarrior863 at gmail.com>wrote:
>>>
>>>> Hi guys.
>>>>
>>>> I've got a doubt regarding the alerts definitions, I have defined
>>>> several alerts for a host, for example one of them is to check if the host
>>>> is up or down, when the host is down I get the alert as usual ans so on,
>>>> but the other alerts get fired as well, service alerts, my question is, if
>>>> is there a way to tell nagios,  if the server is down, do  not tigger the
>>>> other alerts cuz of course are gonna fail?
>>>>
>>>> Thanks for your time and support
>>>> Best Regards
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Minimize network downtime and maximize team effectiveness.
>>>> Reduce network management and security costs.Learn how to hire
>>>> the most talented Cisco Certified professionals. Visit the
>>>> Employer Resources Portal
>>>> http://www.cisco.com/web/learning/employer_resources/index.html
>>>> _______________________________________________
>>>> Nagios-users mailing list
>>>> Nagios-users at 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
>>>>
>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Minimize network downtime and maximize team effectiveness.
>>> Reduce network management and security costs.Learn how to hire
>>> the most talented Cisco Certified professionals. Visit the
>>> Employer Resources Portal
>>> http://www.cisco.com/web/learning/employer_resources/index.html
>>> _______________________________________________
>>> Nagios-users mailing list
>>> Nagios-users at 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
>>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Try New Relic Now & We'll Send You this Cool Shirt
>> New Relic is the only SaaS-based application performance monitoring
>> service
>> that delivers powerful full stack analytics. Optimize and monitor your
>> browser, app, & servers with just a few lines of code. Try New Relic
>> and get this awesome Nerd Life shirt!
>> http://p.sf.net/sfu/newrelic_d2d_apr
>>
>> _______________________________________________
>> Nagios-users mailing list
>> Nagios-users at 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
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20130428/7a3c6eb8/attachment.html>
-------------- next part --------------
------------------------------------------------------------------------------
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service 
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr
-------------- next part --------------
_______________________________________________
Nagios-users mailing list
Nagios-users at 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