> On 02 Feb 2016, at 14:25, René Koch wrote:
>
> Hi list,
>
> I'm testing Icinga 2 and want to achive the following setup:
> 2x Icinga master (notifications, ido db and nsca server)
> 1x Icinga tools server (Icinga web 2 and pnp)
> 3x Icinga worker (active checks)
>
> My 2 master servers are resp
Sehr geehrte Damen und Herren!
Vielen Dank für Ihre Nachricht an das UrlaubUrlaub Team (i...@urlauburlaub.at),
deren Eingang wir hiermit bestätigen.
Wir werden uns so rasch wie möglich um Ihr Anliegen kümmern. Bei Rückfragen
werden wir uns umgehend bei Ihnen melden. Ansonsten erhalten Sie eine
On 02/02/2016 04:20 PM, Michael Friedrich wrote:
On 02 Feb 2016, at 14:25, René Koch wrote:
Hi list,
I'm testing Icinga 2 and want to achive the following setup:
2x Icinga master (notifications, ido db and nsca server)
1x Icinga tools server (Icinga web 2 and pnp)
3x Icinga worker (active chec
On Mon, Feb 01, 2016 at 10:23:49PM +, Michael Friedrich wrote:
> >>> Whats the recommended way for transition?
> >>
> >> Improve your check plugin, or use alternatives. Using modern hardware
> >> it shouldn’t be a matter of resources. Given the fact that Icinga 2
> >> runs multi-threaded and ch
Hi list,
I'm testing Icinga 2 and want to achive the following setup:
2x Icinga master (notifications, ido db and nsca server)
1x Icinga tools server (Icinga web 2 and pnp)
3x Icinga worker (active checks)
My 2 master servers are responsible for sending out notifications and
writing data into I
Hi All,
Sorry for replying my own thread. I tried to play with Icinga 2
configuration. I remove accept_command and accept_config from api.conf
(since the default is false). On master I get this error message :
[2016-02-02 08:29:07 +] notice/JsonRpcConnection: Received
'event::Heartbeat' messag
