Not getting notifications when a service is in an UNKNOWN state

[C. Bensend]

> I am not sure what I'm doing wrong, I get notified when it's warning or
> critical but not unknown... I can't figure out why. Any suggestions?
> Below is the service check.
>
> define service{
>          hostgroup_name hostgroup-win-2003,hostgroup-win-2008
>          service_description     Windows CPU check
>          check_command check_snmp_load_v1!stand!55!95!!$USER2$
>          use                     generic-service-pnp
>          notification_options    u,w,c,r
>          notification_period     workhours
>          contacts                jeremy.page at gilbarco.com
>          check_interval          15
>          retry_check_interval    10
>          }
>
> and the command definition:
> define command {
>          command_name    check_snmp_load_v1
>          command_line    $USER1$/check_snmp_load.pl -H $HOSTADDRESS$ -C
> $ARG5$ -T $ARG1$ -w $ARG2$ -c $ARG3$ $ARG4$ -f
>          }

And your contact definition?



-- 
"The very existence of flamethrowers proves that sometime, somewhere,
someone said to themselves, 'You know, I want to set those people
over there on fire, but I'm just not close enough to get the job
done.'"                          -- George Carlin


------------------------------------------------------------------------------
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_may
_______________________________________________
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