-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 1/27/2014 4:46 PM, Michael Friedrich wrote:
> On 27.01.2014 20:56, Mark Haney wrote:


> 
> No, no and no. Each CheckCommand object is unique by itself. That
> does not make any sense to use one object named "check_nrpe" and
> put multiple command lines into it. How would you reference it by
> its name inside your service definition? That's the exact same
> behavior as known from Nagios / Icinga 1.x
> 
> What Icinga 2 is telling you now is that you've "successfully" 
> overridden your check_nrpe command, and replaced its command with 
> invoking check_pgsql binary which doesn't exist nor is your
> required outcome.
> 
Okay, work with me here.  If I have the check_nrpe CheckCommand object
in place (which I do), what exactly do I need to do to pass the needed
options to the check_pgsql plugin?  Would I create a new Service
object for check_pgsql with the needed macros?  Or would I create a
new CheckCommand object for check_pgsql?

I think what's confusing me is nomenclature as much as process.  With
the check_nrpe command already created, and with a $command$ macro
inside that object, I'm not sure where or how to tell the
'check_pgsql' command what parameters to use.  Would it be considered
a checkcommand object or a service object?

I'm thinking now that the check_nrpe command object is actually
calling a Service object, correct?  If that's the case I would just
need to create a new service object definition for check_pgsql and add
it's required macros to the service object.

Am I getting close?



- -- 
Mark Haney
Network Administrator/IT Support
Practichem
W:919-714-8428
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (MingW32)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJS57S/AAoJEDgEuzPE0JQvVN4IANoRUnwUHI6L86katYp3L+eo
QMGba4QjE1qV9D5KpkcbGL3mLgkw3mlNJrdAJI1VtBbEo6jDB9171gAfWWhQMuN/
x0m0SRV744MhKoE2ebaYWJ2UEC0xmMMahm2wkUS20RoMEB9DlXYSDuw7FuTDbIa/
MWhWXpU7M+8raDlHzFfOlWTG/80fxEBnvq9Xkenq9L2oCsyg/6Aw8qHs/mOX548E
BKdiylT6KM+0JICXCwz4izhHIzhpcrXeHQCW5NILh6rdsc1KfrY63lA7zjIXCmJD
8A8dGMyaPTwopvqGq7EdduWQmHYHRcZDLfXDQKVqc/3NYq6efN1jmjVh8XMnDdw=
=FhdU
-----END PGP SIGNATURE-----

_______________________________________________
icinga-users mailing list
icinga-users@lists.icinga.org
https://lists.icinga.org/mailman/listinfo/icinga-users

Reply via email to