On 17.01.2014 18:21, Mark Haney wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 1/16/2014 4:13 PM, Michael Friedrich wrote:
I didn't see if there was a temporary work around for 0.0.6, not
that it matters.
While the Icinga 2 releases happen on a 3 weeks schedule for our
development sp
On 17.01.2014 20:01, Mark Haney wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This is probably deep down in the docs, but I can't find it.
No it's not. There should be sort of a best practice section like
'connect a remote agent to icinga 2 howto'. Wanna create an issue and
add some t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This is probably deep down in the docs, but I can't find it. How do I
setup NRPE checks in Icinga2? Would I set it up similar to an
existing Icinga2 service in the config:
services["ping4"] = {
templates = [ "generic-service" ],
check_command = "
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 1/16/2014 4:13 PM, Michael Friedrich wrote:
>
>> I didn't see if there was a temporary work around for 0.0.6, not
>> that it matters.
> While the Icinga 2 releases happen on a 3 weeks schedule for our
> development sprints, this is not true for h
There is a simple solution to export to .csv the "Service Log Entries"
table in the "Service Availability Report" page?
Better if parametrizing the start-end time.
I am reading the docs about running the CGIs on the command line, but with
limited results ...
Thanks, Franc.
_
