illegal characters in object

[BenCowan]

Sorry, if this has already been addressed, but I didn't see any specific
match to my issue...

When I first started using XI, I named most my Templates and Commands
to have the first character be an "@". This conveniently floated all my stuff
to the top.

The latest versions of XI, require me to resort to the Legacy CCM, when
updating my configuration.

I saw some posts about this, but just wanted to make sure this will be
corrected down the road, or do I need to start renaming stuff????

[abrist]

The "@" is considered an illegal char for the "config name". So you should start changing names, though you can use the "@" symbol in the alias and the next release will allow the quick find to search aliases. Do note that you should update to 2012R1.3 (if you have not already and can) before you start renaming config names as there was a bug in previous versions that would not allow for config names to be changed cleanly.

[BenCowan]

I'm not trying to be difficult here, and if what you say is true, I can rename everything, however,
I am just trying to understand something. NagiosXI is a tool for configuring Nagios, and also
an alternative monitoring interface.

If having templates and commands beginning with '@' work in Nagios and NagiosXI now, why
do they have to become illegal all of a sudden? Is this a just a limitation of the code for future
enhancements?

[mguthrie]

The reason certain characters are restricted for object names is because they're known to cause unpredictable behavior. This isn't a "new" feature as far as the monitoring engine is concerned, but some javascript sanity checking has been added in order to try and minimize problems caused by special characters.

I might suggest an underscore to accomplish the same thing as the @ character.

[BenCowan]

Ok, thank you.