escalations for passive checks?

[Joel Brooks]

Hi list







i'm messing around with passive checks so that i can integrate sec.pl=
  into nagios to make use of nagios' notification/escalation capabilities
.=

  it seems to me that nagios will only send one notification for=
  each passive check that gets added to the external commands file.=

  i had thought that it would use the whole notification/escalation=
  process after receiving a single CRITICAL event, but it doesn't=
  seem to do that.







here's what i did:







-defined a service (for testing) called 'passive':



define service{



        use                             generic-service



        host_name                       admin



        service_description             passive



        is_volatile                     1



        contact_groups                  production-support



        notification_options            w,u,c,r



        notification_interval           5



        max_check_attempts              1



        check_command                   check_ping



        active_checks_enabled           0



        passive_checks_enabled          1



        }







-define escalations for this service:



define serviceescalation{



        host_name               admin



        service_description     passive



        contact_groups          production-support



        first_notification      2



        last_notification       0



        notification_interval   5



        escalation_period       24x7



        escalation_options      w,u,c,r



}







define serviceescalation{



        host_name               admin



        service_description     passive



        contact_groups          production-support,application-support



        first_notification      5



        last_notification       0



        notification_interval   5



        escalation_period       24x7



        escalation_options      w,u,c,r



}







define serviceescalation{



        host_name               admin



        service_description     passive



        contact_groups          production-support,application-support



        first_notification      7



        last_notification       0



        notification_interval   3



        escalation_period       24x7



        escalation_options      c,r



}







-submit_passive_check:



#!/bin/bash







echocmd="/bin/echo"



cmdfile="/opt/nagios/var/rw/nagios.cmd"



datetime=`date +%s`



cmdline="[$datetime] PROCESS_SERVICE_CHECK_RESULT;$1;$2;$3;$4"



`$echocmd $cmdline >> $cmdfile`







then the test:



./submit_passive_check admin passive 2 00001







this gets logged, and an alert goes out, but no further notifications=
  are sent.  escalations don't do anything because there is never=
  a second notification.







if i do this:



while true; do



 sleep 300



 echo 'submitting passive check...'



 ./submit_passive_check admin passive 2 00001



done







then the notifications work as expected, and the escalations apply.







why doesn't nagios continue to send notifications (and escalations)=
  after the single CRITICAL (non-OK state) event gets logged?  i'm=
  sure this is just my own confusion..







nagios rox btw... great tool!







thx,







- Joel Brooks (joel.brooks)







-----------------------



The mailing list archive is found here:



http://www.nagiosexchange.org/nagios-users.34.0.html



				




-------------------------------------------------------
All the advantages of Linux Managed Hosting--Without the Cost and Risk!
Fully trained technicians. The highest number of Red Hat certifications in
the hosting industry. Fanatical Support. Click to learn more
http://sel.as-us.falkag.net/sel?cmd=lnk&kid7521&bid$8729&dat1642
_______________________________________________
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