Characters not allowed on new CCM but allowed on previous

[johndoe]

This might have been posted before but i couldn't find it...

Until now I was using the old legacy CCM however today I decided to give the new CCM another chance.

Some of our services have names with "[]" that is, we have services like "Backup [Datacenter1]" these run fine on the old CCM however on the new one it claims invalid characters... Am I gonna have to change all my services names and the apps that transmit them to adapt to this annoying limitation on the new CCM?

I'll stick to using the old CCM for now.

Nagios is getting on my nerves so time for a rant...

--- Rant start ---
Everyday more I highly regret ever going the nagios way, the money and time we spent on this tool is just ridiculous.
To nagios staff, get your stuff together, consistency is key for a product. I do not recommend Nagios to anyone at this point, actually since the first 3-4 months of usage... There is no consistency, no decent updates and there seems to be 1000 ways to do the same where following one will most probably end up breaking others.
--- Rant End ---

[abrist]

Some of our services have names with "[]" that is, we have services like "Backup [Datacenter1]" these run fine on the old CCM however on the new one it claims invalid characters

I apologize for these issues. The new CCM has a number of restrictions on nasty meta characters in order to reduce potential exploits. The legacy ccm is still provided for backwards compatibility and legacy installations. There are not any plans to remove these restrictions due to the potential exploits certain meta characters can cause.