Monitoring Parameters

This support forum board is for support questions relating to Nagios XI, our flagship commercial network monitoring solution.
Locked
Nightwing
Posts: 2
Joined: Thu Dec 02, 2021 11:32 am

Monitoring Parameters

Post by Nightwing »

Hello all,

First time posting and a new Nagios XI customer, the server and myself still in our infancy so apologies for any silly questions. I’m finding a lot of support documentation but not finding the answers to my questions and I hope someone can help or point me in the right direction.

System: CentOS Linux 7 - VMWare Image with Nagios XI 5.8.7

Question 1:
When configuring a Host, Configure Host > “Monitoring” and “Notifications”. Under Monitoring you can set “When a potential problem is first detected:” Re-check the host every X minutes up to X times before generating an alert. However, under Notifications When a problem is detected: You have options of not sending a notification, sending immediately and waiting X minutes.

I want the system to re-check the host X minutes before sending a problem alert for small peaks in activity. However, I also have the send Immediately check on. Currently we are getting Problems immediately. What is the relationship between these two tabs? Why isn’t it do the recheck before emailing? Should I be setting the Notifications to don’t notify? Will that not block the email? Should I be calculating the recheck and duration and setting the wait X minutes to match the recheck time?

Question 2:
We’re using Passive Checks with the Agent. I’ve set up the Unconfigured Objects and Auto Configure Settings. I have created a host template called pbl_passive_host. I thought the “Check Settings” tab and fields “Check Internal” “Retry Interval” and “Max Check Attempts” would populate the “Configure Host” > “Monitoring tab” as discussed in Question 1 but these settings are always blank. Is there away to populate these settings?

Thank you in advanced.
Chris
ssax
Dreams In Code
Posts: 7682
Joined: Wed Feb 11, 2015 12:54 pm

Re: Monitoring Parameters

Post by ssax »

1. The check_interval, retry_interval, and max_check_attempts handle the standard notification logic. Additionally, if you wanted to add an additional delay to the first notification, you can set that as well and then after the max_check_attempts is hit it will check to see if the first_notification_delay has been reached, if it hasn't it won't send out the notification until it has.

https://assets.nagios.com/downloads/nag ... tions.html

If you set these:
- Check Interval 5
- Retry Interval 1
- Max Check Attempts 3

It will check the host/service every 5 minutes, if a problem is detected it will check it every 1 minute for 3 checks before a notification is sent.

To increase the delay you could either increase the max_check_attempts or the retry_interval OR use the first_notification_delay option to make sure the notification doesn't go out until it's been in it has been in that state longer than first_notification_delay.

https://assets.nagios.com/downloads/nag ... tions.html

2. Template values are inherited by the objects (you can see the final calculated object in your /usr/local/nagios/var/objects.cache), they aren't directly set on the host/services objects from templates when they are imported. See here for more information:

https://assets.nagios.com/downloads/nag ... tance.html
Locked