[Note - this is a repost in hope of a) reviving the discussion b)
allowing lists.icinga.org to create a full archive of this thread,
which was cut off during the migration. This mail contains all three
mails of the old thread incl. attachments]
On Mon, Jan 13, 2014 at 10:53 PM, Michael Friedrich
Hi,
On 23.01.2014 10:13, Marco Hoyer wrote:
Hi Michael,
I also tried Icinga 2 and am actually building a rpm for icinga web 2. This is
absolutely amazing stuff.
Thanks. I've forwarded that to the team making the magic happen ;-)
I’m really glad that Icinga will cut off some old stuff for f
-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 l
On 28.01.2014 14:46, Mark Haney wrote:
-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 "chec
Hi,
we have a problem that's bugging us for years already, and we don't know
whether it is fixable at all.
We have some services, where we send out alerts to a mobile only when it is
Critical, but not in Warning state. At the same time, we send out email
notifications for all states.
So the esca
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 1/28/2014 9:03 AM, Michael Friedrich wrote:
>
> Same as the already defined service, but with a different name,
> and obviously a different value for the command macro.
>
> services["checkpgsql"] = { templates = [ "generic-service" ],
> notifica
On 28.01.2014 16:24, Mark Haney wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 1/28/2014 9:03 AM, Michael Friedrich wrote:
Same as the already defined service, but with a different name,
and obviously a different value for the command macro.
services["checkpgsql"] = { templates = [
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 1/28/2014 10:25 AM, Michael Friedrich wrote:
>
> services["checkpgsql"] = { templates = [ "generic-service" ],
> check_command = "check_nrpe", macros = { command = "check_pgsql",
> } },
>
> macros = { address = "10.10.10.1", }, }
>
> As it's s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 1/28/2014 10:41 AM, Michael Friedrich wrote:
>> 1 point for me for guessing correctly. You're reaching beer level
>> soon :-P
No problem there. I've got a batch of Winter Ale (which, living near
Raleigh, NC is rather appropriate right now) just ab
On 28.01.2014 16:36, Mark Haney wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 1/28/2014 10:25 AM, Michael Friedrich wrote:
services["checkpgsql"] = { templates = [ "generic-service" ],
check_command = "check_nrpe", macros = { command = "check_pgsql",
} },
macros = { address = "10.1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 1/28/2014 10:47 AM, Mark Haney wrote:
> On 1/28/2014 10:41 AM, Michael Friedrich wrote:
>
>>> 1 point for me for guessing correctly. You're reaching beer
>>> level soon :-P
>
> No problem there. I've got a batch of Winter Ale (which, living
> near
On 28.01.2014 16:47, Mark Haney wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 1/28/2014 10:41 AM, Michael Friedrich wrote:
1 point for me for guessing correctly. You're reaching beer level
soon :-P
No problem there. I've got a batch of Winter Ale (which, living near
Raleigh, NC is
12 matches
Mail list logo
