Page 1 of 1

Stalking in service don't raising further notifications

Posted: Tue Oct 30, 2018 9:06 am
by cmueller
I'm trying to process SNMP traps from an other system. Therefore I configured a SNMP trap definition in the new SNMP trap interface which submits the result to a passive service on a fixed host. Nothing special and working so far.

The configured notification handler is creating a ticket in our ticket system as expected. To reset the service back to OK state I simply added an half hour active check with the check_xi_service_none command. Also working as expected.

Finally I just wanted to ensure that there are more notifications raised if more errors are reported closely after each other. Because the output is changing I configured the stalking option to "Warning","Critical" and "Notification". Unfortunately only the first alert is raising a notification. Further errors with changed outputs are logged but no notification is sent out.

Nagios XI 5.5.2

Code: Select all

define service {
    host_name                 ldefra7710438
    service_description       Dataprotector Session Error
    check_command             check_xi_service_none!!!!!!!!
    max_check_attempts        1
    check_interval            30
    retry_interval            1
    active_checks_enabled     1
    passive_checks_enabled    1
    check_period              24x7
    flap_detection_enabled    0
    notification_period       24x7
    notification_options      w,c,r,
    notifications_enabled     1
    contacts                  ticket-router
    stalking_options          o,w,c,N,
    register                  1
}
Actually I'm not shure if I missed anything within the configuration. Or is there maybe the output only checked for a certain length.
Output and changed output example:
Warning 10/30/2018 13:46 BSM/CSM SessionError "[138:742] Backup session "2018/10/30-19" of the backup specification "MSSQL WDEFRATEMPSQL",backup group "Default" has errors: 3."
;Warning 10/30/2018 13:47 BSM/CSM SessionError "[138:742] Backup session "2018/10/30-20" of the backup specification "MSSQL WDEFRATEMPSQL",backup group "Default" has errors: 3."

Re: Stalking in service don't raising further notifications

Posted: Tue Oct 30, 2018 1:51 pm
by tgriep
Stalking is is more for logging the the check results.

What may help out is to setup Volatile Services.
https://assets.nagios.com/downloads/nag ... vices.html

Volatile services differ from "normal" services in three important ways. Each time they are checked when they are in a hard non-OK state, and the check returns a non-OK state (i.e. no state change has occurred)
the non-OK service state is logged
contacts are notified about the problem (if that's what should be done). Note: Notification intervals are ignored for volatile services.
the event handler for the service is run (if one has been defined)
With this enabled, when multiple Non-OK states are received, it should generate a Notification.

The link provided has more details but I think this is what you are looking for.