Hi,
It seems like Nagios 4 has changed the way that check_command arguments =
are parsed. Overall, this looks like a good thing as I think it looks =
easier to understand as it seems to be much more similar to how the =
shell would evaluate a command. However, I'm worried about the migration =
of existing Nagios configurations.
For instance, this worked in Nagios 3:
----
define service {
...
check_command check_nrpe!-H $HOSTADDRESS$ -c CheckEventLog =
-a file=3DApplication \"filter=3Dgenerated gt -2d AND severity NOT IN =
('success', 'informational')\" MaxWarn=3D1 MaxCrit=3D10
}
define command {
command_name check_nrpe
command_line /usr/local/nagios/libexec/check_nrpe $ARG1$
}
----
In Nagios 4, this fails. To get the same result, you need to configure =
it as:
----
define service {
...
check_command check_nrpe!-H $HOSTADDRESS$ -c CheckEventLog =
-a file=3DApplication "filter=3Dgenerated gt -2d AND severity NOT IN =
('success', 'informational')" MaxWarn=3D1 MaxCrit=3D10
}
----
I can't quite understand the Nagios 3 rules versus the Nagios 4 rules or =
what the conversion process should be. Is there anything that is going =
to be provided for Nagios 4 to ease migrating existing configurations?
Ton
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]