Will service checks send out nofitication ,while host check.

[ahm002]

Will service checks,within a host and already in HARD NON-OK status, send out notification , while the host check is still in SOFT non-OK status checking loop (not reach the MAX_check_attempts)?
We found the service checks will change from SOFT status type to HARD status type immediately when they found the HOST is down(NON-ok status) even the host is still in the retrying loop, and nagios XI wont sent out those service checks alert notifications.
Is it normal?

[cdienger]

A service will go into a HARD state immediate if the HOST is in a DOWN or UNREACHABLE state. This is expected and documented in https://assets.nagios.com/downloads/nag ... types.html.

However, per https://assets.nagios.com/downloads/nag ... tions.html, notifications for services should only be suppressed if the HOST is in a HARD non-OK state.

I know there have been a few tweaks and fixes in the code in recent releases. What version of XI and Core is this? Find out both from the command line with:

Code: Select all

/usr/local/nagios/bin/nagios -V
cat /usr/local/nagiosxi/var/xiversion

[ahm002]

thanks for reply:
we had read those two documents and knew what it means
"A service will go into a HARD state immediate if the HOST is in a DOWN or UNREACHABLE state".
but what we want to ask is if it's true even when HOST is still a in a SOFT DOWN state,within its retry interval ,
not become a HARD DOWN Critical state yet?

"notifications for services should only be suppressed if the HOST is in a HARD non-OK state"
We found out it seems when the HOST is in a SOFT non-OK state, notifications for services will be suppressed too,
so,we want to post question on the forum to ask if anyone has the same experience too,or if it's a normal condition.

here below is result after commands input

/usr/local/nagios/bin/nagios -V
Nagios Core 4.4.5
cat /usr/local/nagiosxi/var/xiversion
cat /usr/local/nagiosxi/var/xiversion
###################################
# DO NOT DELETE THIS FILE!
# Nagios XI version information
###################################
full=5.6.10
major=5
minor=6.10
releasedate=2020-01-16
release=5610

[swolf]

Hi @ahm002,

Our documentation may be slightly out of date. I'll look into getting that fixed.

Here's the rationale for the current behavior:

- If a host is in a DOWN/UNREACHABLE state (including SOFT DOWN), non-OK services will immediately go into a HARD state.
- Because the service immediately goes into a HARD state, Core will try to send notifications for those services.
- At the same time, we want to suppress service notifications in the event that the host state is the cause of the problem (this is written in the documentation as "If the host is in hard non-OK state, notifications for services on this host won't be sent out").
- So, we suppress service notifications for SOFT DOWN hosts as well.

This change was relatively recent (sometime after 4.4.2), so I think you're the first person to catch the discrepancy in the documentation.

Let me know if you need clarification or if you have any other concerns.

[ahm002]

thanks for the explanation.
If the document files have been updated,please let me know, I would like to
read them to give my customers more information about how Nagios is working on
status change and notification .

[benjaminsmith]

Hi,

thanks for the explanation

Your welcome and glad that helped clarify the behavior you were seeing.

I've put a request in to modify the doc, and that should be updated soon.

Let us know if you have any other questions or if it's ok to close out this thread.

Benjamin

[ahm002]

Looking forward to studying the new updated documents.
We know how nagios works with service monitoring notifications now.It's okay to close this thread.

[scottwilkerson]

Looking forward to studying the new updated documents.
We know how nagios works with service monitoring notifications now.It's okay to close this thread.

Great!

Locking thread