Am 24.11.2010 18:38, schrieb marc pascual:


On Thu, Nov 25, 2010 at 1:29 AM, marc pascual <[email protected] <mailto:[email protected]>> wrote:

    Hello mailing list,

    I have set notification_interval on all of my services, but I'm
    still getting notifications on the second and subsequent critical
    alerts. Is there anything else that I need to configure that will
    prevent icinga from sending alerts if the state is pegged on a status?

    [1290618910.256332] [032.0] [pid=9232] ** Service Notification
    Attempt ** Host: 'mickey', Service: 'check_hparray', Type: 0,
    Options: 0, Current State: 2, Last Notification: Wed Nov 24
    12:00:20 2010
    [1290618910.256358] [032.0] [pid=9232] Notification viability test
    passed.
    [1290618910.256365] [032.1] [pid=9232] Current notification
    number: 24 (incremented)
    [1290618910.256373] [032.2] [pid=9232] Creating list of contacts
    to be notified.
    [1290618910.256380] [032.1] [pid=9232] Service notification will
    NOT be escalated.
    [1290618910.256388] [032.1] [pid=9232] Adding normal contacts for
    service to notification list.
    [1290618910.256417] [032.2] [pid=9232] Adding members of contact
    group 'admins' for service to notification list.
    [1290618910.256425] [032.2] [pid=9232] Adding contact
    'icingaadmin' to notification list.
    [1290618910.256442] [032.2] [pid=9232] ** Attempting to notifying
    contact 'icingaadmin'...
    [1290618910.256450] [032.2] [pid=9232] ** Checking service
    notification viability for contact 'icingaadmin'...
    [1290618910.256466] [032.2] [pid=9232] ** Service notification
    viability for contact 'icingaadmin' PASSED.
    [1290618910.256474] [032.2] [pid=9232] ** Notifying contact
    'icingaadmin'
    [1290618910.256500] [032.2] [pid=9232] Raw notification command:
    /etc/icinga/bin/service-alert.pl <http://service-alert.pl> -t
    "$LONGDATETIME$" -h "$HOSTALIAS$" -S "$SERVICEDESC$" -s
    "$SERVICESTATE$" -x "$SERVICEOUTPUT$" -e "$CONTACTEMAIL$"
    [1290618910.256570] [032.2] [pid=9232] Processed notification
    command: /etc/icinga/bin/service-alert.pl
    <http://service-alert.pl> -t "Wed Nov 24 12:15:10 EST 2010" -h
    "mickey" -S "check_hparray" -s "CRITICAL" -x "Smart Array E200i in
    Slot 0    Cache Status: Temporarily Disabled" -e "[email protected]
    <mailto:[email protected]>"
    [1290618910.519850] [032.2] [pid=9232] Calculating next valid
    notification time...
    [1290618910.519924] [032.2] [pid=9232] Default interval: 0.000000
    [1290618910.519946] [032.2] [pid=9232] Interval used for
    calculating next valid notification time: 0.000000
[1290618910.519982] [032.0] [pid=9232] 1 contacts were notified. Next possible notification time: Wed Nov 24 12:15:10 2010

    Regards,
    Marc



p.s. the service confiration:

define service {
        use                     passive
        hostgroup_name          DevQA
        service_description     check_hparray
        servicegroups           check_hparray
        notification_interval   0
        check_command           check_stale_passive
}
I'd have a look at status.dat (or objects.cache) instead to verify which setting is really active.
------------------------------------------------------------------------------
Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
Tap into the largest installed PC base & get more eyes on your game by
optimizing for Intel(R) Graphics Technology. Get started today with the
Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
http://p.sf.net/sfu/intelisp-dev2dev
_______________________________________________
icinga-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/icinga-users

Reply via email to