<div>This is how i wanted to make it look like :</div> <div> </div> <div>[05-19-2009 13:34:00] HOST ALERT: app-engbw5;DOWN;HARD;3;FPING CRITICAL - (loss=100% )</div> [05-19-2009 13:33:00] HOST ALERT: app-engbw5;DOWN;SOFT;2;FPING CRITICAL - (loss=100% ) [05-19-2009 13:32:00] HOST ALERT: app-engbw5;DOWN;SOFT;1;FPING CRITICAL - (loss=100% ) Then at 13:34:00 send out the notification . Is this feasible ?? <div class="gmail_quote">On Tue, May 19, 2009 at 8:47 PM, Dongsheng Song <<a href="mailto:dongsheng.song@gmail.com">dongsheng.song@gmail.com</a>> wrote: <blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">No, please check your "Scheduling Queue", view "Last Check" and "Next Check". Please distinguish "check history" and "alert history". Are you sure you want check max 4 times, and alter every 1 minuties ? The your "check_interval" should be 12s, it's too short! In 'nagios.cfg', set 'interval_length=1'; In host/service template, set: check_interval 12 retry_interval 12 max_check_attempts 3 The the time duration between each alert(not check!) is 1 min . -- Dongsheng Song 2009/5/20 Anirudh Srinivasan <<a href="mailto:srianirudh@gmail.com">srianirudh@gmail.com</a>>: <div> <div></div> <div class="h5">> Hi Dongsheng > > I tried as you suggested by putting > > Check_interval 1 > retry_interval 1 > max_check_attempts 3 > > But this is what i see on the alert history : > > [05-19-2009 13:42:35] HOST ALERT: app-engbw5;DOWN;HARD;3;FPING CRITICAL - > (loss=100% ) > [05-19-2009 13:37:38] HOST ALERT: app-engbw5;DOWN;SOFT;2;FPING CRITICAL - > (loss=100% ) > [05-19-2009 13:32:24] HOST ALERT: app-engbw5;DOWN;SOFT;1;FPING CRITICAL - > (loss=100% ) > > Again the time duration between each check is like 5 min . Its increased now > to 5 min from 3 min > > I want to make it as 1 min and third attempt state as HARD and send > notification. > > > 2009/5/18 Anirudh Srinivasan <<a href="mailto:srianirudh@gmail.com">srianirudh@gmail.com</a>> >> >> Also one more question : >> >> How was nagios managing that retry_interval earlier when this parameter >> was not even set ?? >> >> Is it because of SMART calculation thats set in nagios.cfg ??? If not >> please can i know how that worked ??? >> >> 2009/5/18 Anirudh Srinivasan <<a href="mailto:srianirudh@gmail.com">srianirudh@gmail.com</a>> >>> >>> Hi >>> >>> Thanks for the reply , will try this out. But is there some centralized >>> Parameter in nagios.cfg that could solve this issue. >>> >>> Thanks in Adv >>> >>> On Mon, May 18, 2009 at 11:01 PM, Dongsheng Song >>> <<a href="mailto:dongsheng.song@gmail.com">dongsheng.song@gmail.com</a>> wrote: >>>> >>>> In service definition, set: >>>> >>>> check_interval 1 >>>> retry_interval 1 >>>> max_check_attempts 5 >>>> >>>> >>>> In host definition, set: >>>> check_interval 1 >>>> retry_interval 1 >>>> max_check_attempts 5 >>>> >>>> >>>> You can put them to the host/service template for simplify definition. >>>> >>>> -- >>>> Dongsheng Song >>>> >>>> Anirudh Srinivasan $B<LF;(B: >>>> > Hi Nagios experts: >>>> > >>>> > Below is the Alert history for the the host , and the >>>> > max_check_attemps >>>> > is = 5 >>>> > >>>> > >>>> > [05-11-2009 16:46:57] HOST ALERT: benfwca;DOWN;HARD;5;FPING CRITICAL >>>> > - (loss=100% ) >>>> > [05-11-2009 16:43:36] HOST ALERT: benfwca;DOWN;SOFT;4;FPING CRITICAL >>>> > - (loss=100% ) >>>> > [05-11-2009 16:40:30] HOST ALERT: benfwca;DOWN;SOFT;3;FPING CRITICAL >>>> > -(loss=100% ) >>>> > [05-11-2009 16:37:30] HOST ALERT: benfwca;DOWN;SOFT;2;FPING CRITICAL >>>> > - (loss=100% ) >>>> > [05-11-2009 16:34:16] HOST ALERT: benfwca;DOWN;SOFT;1;FPING CRITICAL >>>> > - (loss=100% ) >>>> > >>>> > If you could notice the check frequency is approx= 3 min . >>>> > >>>> > Is it possible to reduce this parameter, if yes then what is the >>>> > parameter that i have to look for. >>>> > I dont want to reduce the max_check_attemps to a lower value. >>>> > >>>> > All i want to have is check every 1 min for 5 attemps and mark it as >>>> > HARD state. >>>> > >>>> > Is it possible.?? >>>> > >>>> > Thanks in Adv >>>> > -- >>>> > Anirudh Srinivasan >>>> > >>>> >>> >>> >>> >>> -- >>> Anirudh Srinivasan >>> >> >> >> >> -- >> Anirudh Srinivasan >> > > > > -- > Anirudh Srinivasan > > </div></div></blockquote></div> <div></div> -- Anirudh Srinivasan