I have been running 2.5 for quite some time now, and recently decided to upgrade to 3.0 since it was out of the beta phase.<br><br>Everything appears to be working fine from the interface level, but when services are critical, alerts are not sent out.  When I drill down on the service itself, and check for notifications, the "Last Notification" field simply shows:<br>
<br>Current Status:  CRITICAL   (for  2d 14h  4m 43s)<br><<omitted><br>Last Notification:N/A (notification 0)<br><br>The "Notifications" option shows "ENABLED", and so I am a bit confused as to why notifications have not been sent out.<br>
<br>To clarify, host alerts are working just fine, via the check_host_command, but no service alerts are working.  I would appreciate any suggestions.<br><br>Below is an example of how a service is defined, including what I could think of as relevant configuration:<br>
<br>---<br>define contact{<br>        name                            generic-contact<br>        service_notification_period     24x7<br>        host_notification_period        24x7<br>        service_notification_options    w,u,c,r,f,s  <br>
        host_notification_options       d,u,r,f,s<br>        service_notification_commands   notify-service-by-email<br>        host_notification_commands      notify-host-by-email<br>        register                        0<br>
        }<br><br>define contact{<br>        contact_name                    contactname<br>        use                             generic-contact<br>        contactgroups                   sgne<br>        email              &nbsp
 ;            <a href="mailto:contactemail@mydomain.com">contactemail@mydomain.com</a><br>
        }<br clear="all"><br>define contactgroup{<br>        contactgroup_name       sgne<br>        alias                   Network Engineering<br>        }<br><br>define service{<br>        name                            generic-service<br>
        notifications_enabled           1<br>        notification_interval           180<br>        notification_options            w,u,r,f,s<br>        check_freshness                 0<br>        event_handler_enabled           0<br>
        obsess_over_service             0<br>        flap_detection_enabled          1<br>        failure_prediction_enabled      1<br>        process_perf_data               1<br>        retain_status_information       1<br>
        retain_nonstatus_information    1<br>        is_volatile                     0<br>        active_checks_enabled           1<br>        passive_checks_enabled          0<br>        check_period                    24x7<br>
        notification_period             24x7<br>        normal_check_interval           2<br>        max_check_attempts              3<br>        retry_check_interval            1<br>        register                        0<br>
        }<br><br>define service{<br>        name                            service-network<br>        use                             generic-service<br>        service_description             Generic Network Services<br>
        contact_groups                  sgne<br>        register                        0<br>        }<br><br>define hostgroup{<br>        hostgroup_name          sdhq-core<br>        alias                   SDHQ Core Devices<br>
        }<br><br>define host{<br>        use                     host-network<br>        hostgroups              sdhq-core<br>        host_name               <a href="http://device.name">device.name</a><br>        alias                    Core Switch<br>
        address                 <a href="http://device.name.mydomain.com">device.name.mydomain.com</a><br>        }<br><br>define service{<br>        use                     service-network<br>        servicegroups           sdhq<br>
        hostgroups              sdhq-general<br>        service_description     Environmental Checks<br>        check_command           check_snmp_environment!COMMSTRING!cisco<br>        }<br>---<br>