Page 1 of 1
How to find wrongly inherited service source.
Posted: Thu Feb 18, 2021 10:14 am
by kkuznetsov
I have a vCenter monitored via VMware API (
https://assets.nagios.com/downloads/nag ... ios-XI.pdf). However, having selected two services for monitoring only, I see some another "CPU Using" service inherited from somewhere (from some NCPA configuration). I cannot find a source to delete it.
How can I address it? PLease help.
Re: How to find wrongly inherited service source.
Posted: Thu Feb 18, 2021 6:57 pm
by ssax
There's not really a great way to do this, you can do this and that may work for you:
Code: Select all
egrep "{|host_name|service_description|hostgroup_name" /usr/local/nagios/etc/services/*.cfg | grep -B2 hostgroup_name | grep -A1 -B1 'CPU Usage'
If you need help, please PM me a copy of your profile.zip, you can download it from Admin > System Profile by clicking the Download Profile button.
I generally search the configs manually from the profile in order to determine where it's being duplicated.
I have created a feature request to request development add this functionality:
FR: XI - Add am easy method for finding service duplicates and where they are being inherited from
Re: How to find wrongly inherited service source.
Posted: Sat Feb 20, 2021 8:29 pm
by kkuznetsov
Finally, I have found the issue source. The problem was, one of "CPU Usage" services in "Service Management > Managed Hosts" had asterisks (*) sign instead of it's name. It masked all assigned host for this service.
But, it is hard to find such issue if there more than 200 hosts configured. Some tools are required to narrow down such issue localisation.
Thank you, you can lock this branch.
Re: How to find wrongly inherited service source.
Posted: Mon Feb 22, 2021 8:29 am
by scottwilkerson
kkuznetsov wrote:Finally, I have found the issue source. The problem was, one of "CPU Usage" services in "Service Management > Managed Hosts" had asterisks (*) sign instead of it's name. It masked all assigned host for this service.
But, it is hard to find such issue if there more than 200 hosts configured. Some tools are required to narrow down such issue localisation.
Thank you, you can lock this branch.
Closing thread