nagios_parser

nagios_parser copied to clipboard

Nagios status files could contain '\n' in long_plugin_output field. Those values are interpreted as line breaks by the status parser, which leads to plugin output info after '\n' to being...

kovyrin

NagiosParser::Config::Parser.parse only handles last instance of cfg_file or cfg_dir

2

Nagios supports multiple occurrences of the "cfg_file" and "cfg_dir" directives. The parser should probably use an array for values when 2 or more instances of a key are encountered.

osterman

Issues with large status files

2

Parsing takes a huge amount of time (and by huge I mean a few seconds) with even a medium size status file. One thing I'm wanting to use this for...

cpuguy83

Object parse only getting first character for each field

4

The object parser is only pulling the first character for each field: Example: {"use"=>"e", "host_name"=>"5", "alias"=>"B", "address"=>"1", "hostgroups"=>"e", "parents"=>"5"}

cpuguy83