From d41b6d5112afe5b87b80836081fa0263a39e8d91 Mon Sep 17 00:00:00 2001 From: Johannes Meyer Date: Mon, 31 Aug 2015 12:57:41 +0200 Subject: [PATCH] commandtransports.ini: Document how transports are utilized refs #9651 --- modules/monitoring/doc/commandtransports.md | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/modules/monitoring/doc/commandtransports.md b/modules/monitoring/doc/commandtransports.md index db594653c..680f34ca0 100644 --- a/modules/monitoring/doc/commandtransports.md +++ b/modules/monitoring/doc/commandtransports.md @@ -9,12 +9,14 @@ find it under ./modules/monitoring/commandtransports.ini. ## Syntax -You can define multiple command transports in the commandtransports.ini. Icinga -Web 2 will utilize the first transport as the default for a specific Icinga -instance. +You can define multiple command transports in the commandtransports.ini. Every +transport starts with a section header containing its name, followed by the +config directives for this transport in the standard INI-format. -Every transport starts with a section header containing its name, followed by -the config directives for this transport in the standard INI-format. +Icinga Web 2 will try one transport after another to send a command, depending +on the respective Icinga instance, until the command is successfully sent. The +order in which Icinga Web 2 processes the configured transports is defined by +the order of sections in the commandtransports.ini. ## Using a local command pipe