Nagios Support Forum

kenneth59 wrote: ↑Sun Sep 08, 2024 8:15 am Hi,
I have some questions regarding Nagios settings and would appreciate any help.

1. Clarification on "Check Settings" in Nagios:
I’m seeking a clearer understanding of the "check settings" tab in host and service management. While I understand how check intervals, retry intervals, and maximum check attempts work, I’m confused about the options for null, skips, off, and on under check settings.

What do these options mean, and how do they function? I’ve found some forum information on the difference between skips and null, but how do skipping or null differ from simply turning the checks on or off? Could someone provide more detailed explanations or point me to relevant resources?

Below is the forum I found explaining the difference between null and skip:
viewtopic.php?t=8948

I also found some mention of skip in this documentation:
https://assets.nagios.com/downloads/nag ... gement.pdf


2. Event Handler Behavior and Timing:
I’d also like to ask about event handlers in Nagios. From what I’ve read on the Nagios website and based on my understanding, it seems that the event handler is a state-based event, meaning it fires immediately when there’s a change in the service or host state.

Is there any way to configure the event handler to follow the check intervals, retry intervals, and maximum check attempts? For example, instead of triggering the event handler immediately when there’s a state change, can it be set to wait until the state is confirmed after the configured check intervals or retry attempts?

Below is where I got the information on event handlers: https://assets.nagios.com/downloads/nag ... dlers.html

Is there any way to configure the event handler to follow the check intervals, retry intervals, and maximum check attempts? For example, instead of triggering the event handler immediately when there’s a state change, can it be set to wait until the state is confirmed after the configured check intervals or retry attempts?

sgardil wrote: ↑Mon Sep 09, 2024 11:08 am As for the event handlers you are right that it will fire immediately on the state change. To get what you want you would want to make sure that the event handler you are using only runs on a hard state. Theres a link in the documentation you posted that explains the differences between soft and hard states fairly well.

snapier3 wrote: ↑Mon Sep 09, 2024 11:40 am Your handler is where you work with this logic.

Using the Nagios macros you can pass the needed variables to the command that executes your handler.
https://assets.nagios.com/downloads/nag ... olist.html

You can use the HARD/SOFT designation from $HOSTSTATETYPE$ or $SERVICESTATETYPE$ to determine the point in the check process you're at.

You can use $MAXHOSTATTEMPTS$ vs $HOSTATTEMPT$ macro values to understand the number of iterations of the host check and $MAXSERVICEATTEMPTS$ /$SERVICEATTEMPT$ to do the same for services.

Small Note: Nagios Core 4.5.0 added enhancements for handler time period changes.
https://www.nagios.org/projects/nagios-core/4x/

--SN

sgardil wrote: ↑Mon Sep 09, 2024 11:08 am
From my understanding skip and null differ from on and off in the sense that they are changing the values from any template inheritance you may have. For example when you have skip it will inherit the value of a template if there is one but not turn it on if there is not. Where as null will make it so that it will not inherit the value from the template.

• If I set "event handler enable" to null, the service will use its own event handler, which is the "service handler."

• If I set "event handler enable" to skip, the service will use the inherited event handler, which is the "inherited handler."

• I assume setting "event handler enable" to off will completely stop the handler from being triggered, meaning neither the "service handler" nor the "inherited handler" will be triggered.

• If I set "event handler enable" to on, it will first use the "service handler." If the "service handler" is missing, it will fall back to the "inherited handler."

Assuming that this service has an event handler from a linked template and also has its own event handler configured, I will refer to the handler inherited from the template as the "inherited handler" and the service’s own handler as the "service handler."

kenneth59 wrote: ↑Thu Sep 12, 2024 10:30 pm Hi sgardil,

Do correct me if I misunderstood what you mean.
Assuming that this service has an event handler from a linked template and also has its own event handler configured, I will refer to the handler inherited from the template as the "inherited handler" and the service’s own handler as the "service handler."

• If I set "event handler enable" to null, the service will use its own event handler, which is the "service handler."

• If I set "event handler enable" to skip, the service will use the inherited event handler, which is the "inherited handler."

• I assume setting "event handler enable" to off will completely stop the handler from being triggered, meaning neither the "service handler" nor the "inherited handler" will be triggered.

• If I set "event handler enable" to on, it will first use the "service handler." If the "service handler" is missing, it will fall back to the "inherited handler."

Is this understanding correct?

• null: Will use the local event handler, even if no event handler is set.

• off: Will completely disable the event handler, preventing it from being triggered.

• skip and on: Will take the handler from the template.

• skip and on: Will use the local event handler.