Weird notification issue!

[BanditBBS]

Here are the real results of Troy's requested commands against the proper objects cache

First two:

Code: Select all

[nagios@iss-chi-nag05 newservers]$ cat /var/nagiosramdisk/objects.cache | sed -rn "/define host \{/{:a;N;/}/{/.host_name.extn-chi-pdb02/p;d};ba}"
define host {
        host_name       extn-chi-pdb02
        alias   extn-chi-pdb02(PRODEBS2)
        address 10.160.101.17
        check_period    xi_timeperiod_24x7
        check_command   check_xi_host_ping!3000.0!80%!5000.0!100%!!!!
        contacts        extn_nagios_db
        contact_groups  EXTN_NAGIOS_ALL_CG,EXTN_NAGIOS_ALL_CG
        notification_period     xi_timeperiod_24x7
        initial_state   o
        importance      0
        check_interval  5.000000
        retry_interval  1.000000
        max_check_attempts      2
        active_checks_enabled   1
        passive_checks_enabled  1
        obsess  1
        event_handler_enabled   1
        low_flap_threshold      0.000000
        high_flap_threshold     0.000000
        flap_detection_enabled  1
        flap_detection_options  a
        freshness_threshold     0
        check_freshness 0
        notification_options    a
        notifications_enabled   1
        notification_interval   0.000000
        first_notification_delay        0.000000
        stalking_options        n
        process_perf_data       1
        retain_status_information       1
        retain_nonstatus_information    1
        }
[nagios@iss-chi-nag05 newservers]$ cat /var/nagiosramdisk/objects.cache | sed -rn "/define host \{/{:a;N;/}/{/.host_name.extn-chi-pdb05/p;d};ba}"
define host {
        host_name       extn-chi-pdb05
        alias   extn-chi-pdb05(ASCP)
        address 10.160.101.20
        check_period    xi_timeperiod_24x7
        check_command   check_xi_host_ping!3000.0!80%!5000.0!100%!!!!
        contacts        extn_nagios_db
        contact_groups  EXTN_NAGIOS_ALL_CG,EXTN_NAGIOS_ALL_CG
        notification_period     xi_timeperiod_24x7
        initial_state   o
        importance      0
        check_interval  5.000000
        retry_interval  1.000000
        max_check_attempts      2
        active_checks_enabled   1
        passive_checks_enabled  1
        obsess  1
        event_handler_enabled   1
        low_flap_threshold      0.000000
        high_flap_threshold     0.000000
        flap_detection_enabled  1
        flap_detection_options  a
        freshness_threshold     0
        check_freshness 0
        notification_options    a
        notifications_enabled   1
        notification_interval   0.000000
        first_notification_delay        0.000000
        stalking_options        n
        process_perf_data       1
        retain_status_information       1
        retain_nonstatus_information    1
        }

Second Two:

Code: Select all

define service {
        host_name       extn-chi-pdb02
        service_description     PRODEBS - Database Alert Log Errors
        check_period    xi_timeperiod_24x7
        check_command   check_by_ssh_dblog!/us1001/app/oracle/diag/rdbms/prodebs/PRODEBS2/trace/alert_PRODEBS2.log!ORA!-c 1!!!!!
        contacts        extn_nagios_db
        contact_groups  EXTN_NAGIOS_ALL_CG,EXTN_NAGIOS_ALL_CG
        notification_period     xi_timeperiod_24x7
        initial_state   o
        importance      0
        check_interval  5.000000
        retry_interval  2.000000
        max_check_attempts      1
        is_volatile     0
        parallelize_check       1
        active_checks_enabled   1
        passive_checks_enabled  1
        obsess  1
        event_handler_enabled   1
        low_flap_threshold      0.000000
        high_flap_threshold     0.000000
        flap_detection_enabled  0
        flap_detection_options  a
        freshness_threshold     0
        check_freshness 0
        notification_options    r,w,u,c
        notifications_enabled   1
        notification_interval   0.000000
        first_notification_delay        0.000000
        stalking_options        n
        process_perf_data       1
        retain_status_information       1
        retain_nonstatus_information    1
        }

define service {
        host_name       extn-chi-pdb05
        service_description     PRODASCP - Database Alert Log Errors
        check_period    xi_timeperiod_24x7
        check_command   check_by_ssh_dblog!/us1001/oracle/db/tech_st/11.1.0/admin/PRODASCP_extn-chi-pdb05/diag/rdbms/prodascp/PRODASCP/trace/alert_PRODASCP.log!ORA!-c 1!!!!!
        contacts        extn_nagios_db
        contact_groups  EXTN_NAGIOS_ALL_CG,EXTN_NAGIOS_ALL_CG
        notification_period     xi_timeperiod_24x7
        initial_state   o
        importance      0
        check_interval  5.000000
        retry_interval  2.000000
        max_check_attempts      1
        is_volatile     0
        parallelize_check       1
        active_checks_enabled   1
        passive_checks_enabled  1
        obsess  1
        event_handler_enabled   1
        low_flap_threshold      0.000000
        high_flap_threshold     0.000000
        flap_detection_enabled  0
        flap_detection_options  a
        freshness_threshold     0
        check_freshness 0
        notification_options    r,w,u,c
        notifications_enabled   1
        notification_interval   0.000000
        first_notification_delay        0.000000
        stalking_options        n
        process_perf_data       1
        retain_status_information       1
        retain_nonstatus_information    1
        }

[BanditBBS]

Once an escalation is triggered, original contacts are not notified any longer unless they are part of the escalation

Scott. I keep going back in my head to this statement. Maybe the one that is "working" is a fluke and my notifications are acting as they should. I have notifications set with interval 0 so only one is going out. I recently added these escalations into the mix because a couple people wanted notifications only for their prod servers, so I did that through escalations instead of templates.

If notifications do in fact behave how you said in what I quoted, I guess I should use a separate PROD template and NON-PROD template then?!?!??! Then remove the escalations and everything will then operate as I desire. That sound right?

EDIT: If that is indeed the case, thats fine. I just created a couple new templates and added 1 or 2 more templates to hosts that needed them and believe I am getting the desired effect and you can close this mess of a thread