On 20.01.2014 16:55, Mark Haney wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 1/20/2014 10:43 AM, Michael Friedrich wrote:
Both work. While the snapshot package will show the timestamp it
was built, the binary version will tell about the git commit hash
it's sources are based on.
And you should provide both so that devs may easily identify your
version in case of any bugs.
One thing, real quick, where would I put the CheckCommand object?:
object CheckCommand "check_nrpe" inherits "plugin-check-command" { ... }
Inside it's own file in /etc/icinga2/conf.d? Or in an existing config
file like generic-service?
Icinga 2 doesn't care as long as it's included. The config parser reads
all objects into memory and then tries to find relationships - so the
order of inclusion doesn't matter, as long as it's included.
If you happen to have a file named "commands.conf" where you'll add all
your commands, it's a possible strategy.
Others then to create directories with file names based on services,
such as nrpe.conf and add all commands and host/services over there.
That's actually something you should design / decide. But probably some
more best practices are needed.
ding-dong: https://dev.icinga.org/issues/5505
kind regards,
Michael
--
DI (FH) Michael Friedrich
mail: michael.friedr...@gmail.com
twitter: https://twitter.com/dnsmichi
jabber: dnsmi...@jabber.ccc.de
irc: irc.freenode.net/icinga dnsmichi
icinga open source monitoring
position: lead core developer
url: https://www.icinga.org
_______________________________________________
icinga-users mailing list
icinga-users@lists.icinga.org
https://lists.icinga.org/mailman/listinfo/icinga-users
