Hi,
We are thinking of enabling our deadpool setting but are a little unsure about the impact it may have.
I see it is a two stage process, after the first x days the host/service is moved to the deadpool. Then after y days they get automatically deleted from the system.
For the hosts, we are OK. If it is not responding for a long period then it's been decommissioned and the engineer forgot to remove it.
But for services we are not OK. It may be that a service is in problem state but the resolution is waiting on a 3rd party to do their bit. So, not ideal, but it may take some time to fully resolve.
Question - can you set an exclusion filter to exclude ALL services? I've tried on our test box using the exclusion filter * but still the services get put into the dead pool. Or is there a way of saying - "don't process for services" ?
Thanks
Live system 2014R2.0 (which I've not tested this on).
Test system 5.2.8
Deadpool - question
Re: Deadpool - question
You should be able to use /.*/ for the "Exclusion Filters" to match every service. Though I haven't spent much time testing that; Only just now configuring it in my lab machine.
Though if you're deleting the host and not the services, there's a good chance your configuration set will be a bit messed up. Services need to be assigned to a host object.
Though if you're deleting the host and not the services, there's a good chance your configuration set will be a bit messed up. Services need to be assigned to a host object.
Former Nagios employee
https://www.mcapra.com/
https://www.mcapra.com/
-
avandemore
- Posts: 1597
- Joined: Tue Sep 27, 2016 4:57 pm
Re: Deadpool - question
Neither of those worked for me.
I've also tried a few others. The only exclusion I could get to work is to put the entire service description string in the exclusion box.
So for now I've chosen to set the number of days to 9999. That will give plenty of time before services end up in the deadpool !!!
Thanks for the suggestions.
I've also tried a few others. The only exclusion I could get to work is to put the entire service description string in the exclusion box.
So for now I've chosen to set the number of days to 9999. That will give plenty of time before services end up in the deadpool !!!
Thanks for the suggestions.
Steve
Re: Deadpool - question
Update
======
This got my curiosity as no variation of a regex expression worked. After some digging, I think I've found an issue in deadpool.php (/usr/local/nagiosxi/cron/deadpool.php).
So our test system is XI v5.2.8, looking at deadpool.php and lines around 378. This section is labelled 'check service filters'. But the regex match (line 388) is using the host filter and hostname, just like on line 369 in the host filter section !!!
Thinking that this may have been addressed in a later version, I downloaded v5.4.2 and extracted it. Loaded deadpool.php in an editor and although the line numbers are different, go to line 369, the same issue is there.
======
This got my curiosity as no variation of a regex expression worked. After some digging, I think I've found an issue in deadpool.php (/usr/local/nagiosxi/cron/deadpool.php).
So our test system is XI v5.2.8, looking at deadpool.php and lines around 378. This section is labelled 'check service filters'. But the regex match (line 388) is using the host filter and hostname, just like on line 369 in the host filter section !!!
Thinking that this may have been addressed in a later version, I downloaded v5.4.2 and extracted it. Loaded deadpool.php in an editor and although the line numbers are different, go to line 369, the same issue is there.
Steve
Re: Deadpool - question
Hi Steve,
Looks like you nailed it. I've filed task ID 11301 with our dev team to fix it.
Looks like you nailed it. I've filed task ID 11301 with our dev team to fix it.
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.