This is sort of an extension of the better password support post.
The Idea: Allow unhindered input when naming anything in Nagios.
The Purpose: To allow ease of wizard use and data input.
The Why: I just attempted to input a switch (via wizard) that had one port name with (Test) in it which caused the config apply to fail. I do sysadmin and programming for a living so I understand what an undertaking it can be to add this sort of support, but its basically become one of those Programming 101 rules. There should be code somewhere to handle non-alphanumeric input.
Better input handling for services and hosts!
-
- Posts: 316
- Joined: Thu Mar 31, 2011 9:54 am
- Location: Patten, ME
- Contact:
Re: Better input handling for services and hosts!
This code does exist, however Nagios Core has some naming restrictions.
Nagios Core (in the nagios.cfg file):
Most of these characters because problematic on the shell, which is why they're not allowed in host names or service descriptions.
Nagios Core (in the nagios.cfg file):
Code: Select all
illegal_object_name_chars=`~!$%^&*|'"<>?,()=