--=_053aa18975edc7ddb0d3a0e574090763
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Hi List,=20
I'm using NRPE as the default client installed on *nix machines.=20
I think key in each monitoring system is that you need to be able to
define your thresholds on the level of your monitoring system itself, and
not on the clients.
(Whether monitoring results are evaluated by the monitoring system or by
the monitoring client, that's another story.)=20
In other words we're using the "dont_blame_nrpe" parameter on all my
clients, which offers for us a very powerfull and flexible setup.
I (personally) think is the minimum you can expect of a monitoring system
is that you don't need to be on the client side to define thresholds.=20
Anyhow, ... I came to a point where I need to send over regular
expressions over nrpe to the remote client, which fails of course because
of the hard coded "illegal metacharacters"=20
Now my request:
* It would be nice, if these characters could be defined in the config
file, giving a user control.
* How can I change the code so these metachars are
ignored?=20
Isn't there a security design which allows such functionality while it
being secure?=20
Thanks,=20
Jelle Smet
http://www.smetj.net
=20
--=_053aa18975edc7ddb0d3a0e574090763
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html; charset="UTF-8"
Hi List,
I'm using NRPE as the default client installed on *nix machines.
I think key in each monitoring system is that you need to be able to def=
ine your thresholds on the level of your monitoring system itself, and not =
on the clients.
(Whether monitoring results are evaluated by the monit=
oring system or by the monitoring client, that's another story.)
In other words we're using the "dont_blame_nrpe" parameter on all my cli=
ents, which offers for us a very powerfull and flexible setup.
I (pers=
onally) think is the minimum you can expect of a monitoring system is that =
you don't need to be on the client side to define thresholds.
Anyhow, ... I came to a point where I need to send over regular expressi=
ons over nrpe to the remote client, which fails of course because of the ha=
rd coded "illegal metacharacters"
Now my request:
* It would be nice, if these characters could be de=
fined in the config file, giving a user control.
* How can I change th=
e code so these metachars are ignored?
Isn't there a security design which allows such functionality while it b=
eing secure?
Thanks,
Jelle Smet
http://www.smetj.net
--=_053aa18975edc7ddb0d3a0e574090763--
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]