This would work perfectly for us. Where can I find the password to access the mysql tables so I can make this alter? And will this affect support at all?mguthrie wrote:Interesting trick we discovered from this thread. If you're using *only* service->hostgroup assignments in a service definition, you can actually pass exclusions as a free variable and Nagios Core will honor the definition. So if you don't have any inclusive host assignments in a service definition you could add as a free variable:
host_name
!host1,!host2,!host3
You would of course be subject to the VARCHAR limit of that table, but that could easily be remedied with an ALTER TABLE query.
Imported Configuration Truncated?
Re: Imported Configuration Truncated?
Re: Imported Configuration Truncated?
Tested and this should get you what you need. If you need more than 1024 go ahead and bump it up larger.
This is such a minor alteration it shouldn't have any adverse effects for the software or support. We'll definitely tell you if it's something that affects support 
Code: Select all
mysql -pnagiosxi nagiosql
ALTER TABLE tbl_variabledefinition MODIFY COLUMN value varchar(1024);

Re: Imported Configuration Truncated?
Glad to be of help! I have this in operation now.. There's more to do, of course, but the config is loaded now.. yay!mguthrie wrote:Interesting trick we discovered from this thread. If you're using *only* service->hostgroup assignments in a service definition, you can actually pass exclusions as a free variable and Nagios Core will honor the definition. So if you don't have any inclusive host assignments in a service definition you could add as a free variable:
host_name
!host1,!host2,!host3
You would of course be subject to the VARCHAR limit of that table, but that could easily be remedied with an ALTER TABLE query.
Now on to making our various plugins work...
Thanks for the help!