Hello. I have been using the import tool quite a bit on the latest version (which at time of writing is 3.0.3). I would happily file bug reports but I seam unable to access that part of the site, even with a registered account.

1) If I name my service file "My Service File" it will happily import my services and the NagiosQL "Config Name" will be "My Service File" with spaces in it. When I add a new service, the Config Name can not have spaces in it. If I try to edit the Service that has the config name of "My Service File" it errors out until I remove the spaces. The config and config generator work just fine with spaces (at least I have not noticed any problems).

2) In the same "My Service File" if my services has a +servicegroup
the "+" is not included in the GUI. However it is included in the config generator. So:

"My Service File".cfg
define service {
service_description Mem Usage
use mem-tmpl
hostgroup_name win-basic
service_groups +mem-dev
}

Imported, in the NagiosQL Gui I do not see the "+" under service groups. But the config generated looks like this:

define service {
hostgroup_name win-basic
service_description Mem Usage
use mem-tmpl
service_groups +mem-dev
register 1
}

3) In a service, the "service_description" is aka "description"
originally my services.cfg were all using "description" which the import tool ignores. Not a big deal, changed it to service_description.

4) Nagios will happily work with no Alias (Description in NagiosQL) set for hosts, hostgroups, and servicegroups. Is there a reason why they are "Required" for NagiosQL? I basically set all my alias's to be the same as the host/hostgroup/servicegroup. Is there an option somewhere I am missing?

5) Is there a way I can turn off the notification that "You have not filled in the required Fields"? with many templates nothing is complete on any one of them. So I have to click YES quite a bit.

6) NagiosXI has moded nagiosQL and their version of is, when you write a config file, it writes ALL the config files, every time. This is a great idea. There should be an option for this.

7) Lastly I was thinking about an easy way to manage distributed nagios monitoring with nagiosql. I think the easiest way, would be to add a "Config Name" type setting to Hosts and hostgroups. The commands, timeperiods, contacttemplates, contacts, contactgroups, hosttemplates, servicetemplates, services, and servicegroups would all be the same on all boxes. The only difference would be which hosts, and hostgroups each nagios box contacts. Then it would be a matter of looping through the hosts and making sure all the parents are also available. Hopefully that makes sense. If I knew php better I would try and take a crack at it myself.

Thanks for making NagiosQL, I think it is the best Nagios Configurator out there, and I've tried them all.

1)Config Name is an internal value of NagiosQL - Nagios does not use this. Because the config name is also the file name of the configuratione file, the charset is restricted to "safe characters" for filenames. We do not want spaces in filenames.

2) The + is visible in the GUI below the value box - there are tree radio buttons for "+", "null" or "Standard" - klick to the "?" beside them for a description.

3) We support only the keyfields written inside the official nagios documentation:
nagios.sourceforge.net/docs/3_0/objectdefinitions.html#service
If you use "working but undocumented directives" - this is at your own risk.

4) "Red marked directives" inside the official Nagios documentation are "required fields" in NagiosQL. The documentation says:
"Note: Directives in red are required, while those in black are optional."
nagios.sourceforge.net/docs/3_0/objectdefinitions.html#host
nagios.sourceforge.net/docs/3_0/objectde...tions.html#hostgroup
nagios.sourceforge.net/docs/3_0/objectde...ns.html#servicegroup

5) It could be a good idea to introduce in 3.1 an option, whether these warnings will be displayed or not. I wrote this in the wishlist.

6) There is an option under "Tools"-"Nagios control" with which you can write all the monitoring data, or any additional data. This is the same. We don not want to do this all time, because it needs much time in big environments.

7) We consider this issue for 3.1. Exactly how it is implemented at the moment is not yet decided

1) it's no problem if you do not want spaces in the Config name. I'm telling you that the Import tool will import service files with spaces in the name, and then there will be spaces in the config name. Which then causes issues if you try to edit any of the file with spaces. Perhaps the import tool needs to be changed to not allow spaces in file names? Or a warning when it detects spaces? Or adds a dash or underscore or something before it writes a config name with spaces.

2) I know where the radio buttons are, sorry I wasn't very clear in the last message. I'll try again.

I import:
"My Service File".cfg
define service {
service_description Mem Usage
use mem-tmpl
hostgroup_name win-basic
service_groups +mem-dev
}

In the NagiosQL gui the import works, but in the GUI, under service groups, the radio button is set to standard.

When I generate a config, it looks like this:

define service {
hostgroup_name win-basic
service_description Mem Usage
use mem-tmpl
service_groups +mem-dev
register 1
}

So; is the standard additive, or is this a display bug in the gui? It seams to be using the correct settings but it is not displaying them in the gui. (Unless the standard is additive).

Thanks for the response on the other items.

have a good day.

1) I will check that in our importer script.

2) Does this error affects only the field "service groups" within the service configuration or this is especially true for other select fields?

Okay, I just tested this a few times:

I Import ONLY this file:

deleteme.cfg:
define service {
service_description deleteme1
use deleteme2
hostgroup_name +deleteme3
service_groups +deleteme4
}

In the NagiosQL GUI:
Supervision->Services->Configname=deleteme, servicename=deleteme1

The hostgroups radio button is set to "+" but no hostgroups are selected
The servicegroups radio button is set to standard, and no servicegroups are selected.

Supervision->Host groups->deleteme3
hostgroup exists, no members or hostgroup members are set.

Supervision->Service groups: There is no record of deleteme4

Supervision->Service Templates->deleteme2
the template has been created, the only thing set is the template name.


If I write the configs, ~nagiosql/services/deleteme.cfg =

define service {
hostgroup_name +deleteme3
service_description deleteme1
use deleteme2
service_groups +deleteme4
register 1
}

So it seams the database is being setup correctly, but something in the gui isn't quite working right. (at least from my perspective).

If there is any further testing I can do, please let me know.

This is partially correct.

If you import a service object whis uses "not known" sub objects (hostgroups, servicegroups, service templates), NagiosQL creates a "dummy" object for all these. This dummy objects are inactive as long as you do not import them correctly.

The service GUI does only show "active" objects - so all these dummy objects are not visible (but in database). If you save this service object in this state - the dummy objects will lost.

So you should import all used objects before you edit or show something.

The only bug is, that there is no dummy service group.

We will check this.