Page 1 of 1
import failed with exclamation mark
Posted: Wed Jan 10, 2018 9:57 am
by sltn_support
Hi,
I've create a service and in this service I excluded some hosts.
But when I want to import this file (trough ccm) I get:
"You must enter a proper host name. You can not use the characters: \~!$%^&*"'|<>?()="
This is the config file:
define service {
host_name !s001v,!s002v,!s003v
service_description Service: Windows Update
use st_alert_p2,st_check_15-5-6
hostgroup_name 04_microsoft_windowsserver_2008
check_command check_nt_service_1.2_v2c_sltn!"Windows Update"!!!!!!!
process_perf_data 1
register 1
}
Re: import failed with exclamation mark
Posted: Wed Jan 10, 2018 11:48 am
by lmiltchev
The CCM import tool doesn't support group exclusions, at least, not yet.
example01.PNG
What you can do is import the service config without exclusions, then modify the service in the CCM to exclude the three hosts - s001v, s002v, and s003v.
CCM > Services > Windows Update > Manage Hosts > Add Selected > select the "Exclude" check-box > Close > Save > Apply Configuration
Re: import failed with exclamation mark
Posted: Wed Jan 10, 2018 2:29 pm
by sltn_support
lmiltchev wrote:The CCM import tool doesn't support group exclusions, at least, not yet.
example01.PNG
What you can do is import the service config without exclusions, then modify the service in the CCM to exclude the three hosts - s001v, s002v, and s003v.
CCM > Services > Windows Update > Manage Hosts > Add Selected > select the "Exclude" check-box > Close > Save > Apply Configuration
Ok but this is just an example. I have like +- 150 servers to exclude everytime.
So Nagios has his own export and import tool but it is not working 100%
Re: import failed with exclamation mark
Posted: Wed Jan 10, 2018 3:25 pm
by lmiltchev
I understand this is going to be a tedious process in large environments, but again, as of now, importing group exclusions is not supported yet. I filed an internal feature request for adding this functionality to the CCM import tool, which is pending approval.
As a "workaround" for the time being, you could manage these hosts/services manually by placing the configs in the static directory. For more information on the manual config file management in Nagios XI, please review our KB article on the topic here:
https://support.nagios.com/kb/article/n ... t-160.html