Le module architecture-export effectue deux types d'actions distinctes :

  • Modification de la configuration de NagVis afin de permettre la communication entre NagVis et Shinken
  • Création des cartes d'une architecture Shinken pour NagVis

Chaque action est retranscrite dans les logs de l'arbiter



Les logs de modification de la configuration de NagVis

Lecture de la configuration du module

Au démarrage du module, celui-ci va commencer par lire sa propre configuration afin de vérifier que les informations sont bonnes (voir Module architecture-export)

En INFO seront affichés les étapes de lecture de la configuration. En DEBUG seront affichés les détails de lecture de la configuration, tels que les paramètres récupérés.

Exemple

Voici un exemple d'une lecture de configuration du module ayant réussie

[AAAA-MM-DD HH:MM:SS] INFO   : [ arbiter ] [ ARCHITECTURE-EXPORT ] [ READING CONFIGURATION ] Broker found from parameter [ architecture_export__broker_connection__broker_name ]
[AAAA-MM-DD HH:MM:SS] DEBUG  : [ arbiter ] [ ARCHITECTURE-EXPORT ] [ READING CONFIGURATION ] Broker [ broker ] found
[AAAA-MM-DD HH:MM:SS] INFO   : [ arbiter ] [ ARCHITECTURE-EXPORT ] [ READING CONFIGURATION ] WebUI module found from parameter [ architecture_export__broker_connection__broker_webui ]
[AAAA-MM-DD HH:MM:SS] DEBUG  : [ arbiter ] [ ARCHITECTURE-EXPORT ] [ READING CONFIGURATION ] The WebUI address is [ localhost ], we will use its public address [ 192.168.1.119 ] for WebUI redirection
[AAAA-MM-DD HH:MM:SS] DEBUG  : [ arbiter ] [ ARCHITECTURE-EXPORT ] [ READING CONFIGURATION ] WebUI [ WebUI ] found, its address is http://192.168.1.119:7767
[AAAA-MM-DD HH:MM:SS] DEBUG  : [ arbiter ] [ ARCHITECTURE-EXPORT ] [ READING CONFIGURATION ] The Livestatus address is [ localhost ], we will use its public address [ 192.168.1.119 ] for WebUI redirection
[AAAA-MM-DD HH:MM:SS] INFO   : [ arbiter ] [ ARCHITECTURE-EXPORT ] [ READING CONFIGURATION ] Livestatus module found from parameter [ architecture_export__broker_connection__broker_livestatus ]
[AAAA-MM-DD HH:MM:SS] DEBUG  : [ arbiter ] [ ARCHITECTURE-EXPORT ] [ READING CONFIGURATION ] Livestatus [ Livestatus ] found, its address is 192.168.1.119:50000


Cas d'erreurs

Si le Broker renseigné dans le paramètre architecture_export__broker_connection__broker_name est introuvable, l'édition du fichier de configuration de NagVis sera annulée et ce message apparaîtra

[AAAA-MM-DD HH:MM:SS] ERROR  : [ arbiter ] [ ARCHITECTURE-EXPORT ] [ READING CONFIGURATION ] The broker [ broker ] set with parameter [ architecture_export__broker_connection__broker_name ] do not exists. Abort edition of the nagvis config file


Si le paramètre architecture_export_broker_connection_broker_webui_communication_type est à "module" et que le module WebUI renseigné dans le paramètre architecture_export_broker_connection_broker_webui_target est introuvable, l'édition de la configuration de la communication entre NagVis et le module WebUI sera annulée et ce message apparaîtra

[AAAA-MM-DD HH:MM:SS] ERROR  : [ arbiter ] [ ARCHITECTURE-EXPORT ] [ READING CONFIGURATION ] The WebUI module [ WebUI ] set with parameter [ architecture_export__broker_connection__broker_webui_target ] do not exists on the Broker [ broker-master ], we will not change the configuration of the communication between NagVis and the WebUI


Si le module Livestatus renseigné dans le paramètre architecture_export__broker_connection__broker_livestatus est introuvable, l'édition de la configuration de la communication entre NagVis et le module Livestatus sera annulée et ce message apparaîtra

[AAAA-MM-DD HH:MM:SS] ERROR  : [ arbiter ] [ ARCHITECTURE-EXPORT ] [ READING CONFIGURATION ] The Livestatus module [ Livestatus ] set with parameter [ architecture_export__broker_connection__broker_livestatus ] do not exists on the Broker [ broker-master ], we will not change the configuration of the communication between NagVis and the Livestatus


Edition/Lecture de la configuration de NagVis

Après la lecture de la configuration du module, celui-ci va être face à deux options :

  • Si la configuration est bonne, il va modifier la configuration de NagVis pour être en accord avec la sienne
  • Sinon, il va simplement lire la configuration de NagVis afin de connaître son état actuel

En INFO seront affichés les différentes étapes. En DEBUG seront affichés les détails, tels que les paramètres récupérés.

Exemples

Voici un exemple d'une modification de la configuration de NagVis ayant réussie

[AAAA-MM-DD HH:MM:SS] INFO   : [ arbiter ] [ ARCHITECTURE-EXPORT ] [ nagvis-shinken-architecture ] [ CONFIGURATION ] UPDATING connection between NagVis and Shinken modules
[AAAA-MM-DD HH:MM:SS] INFO   : [ arbiter ] [ ARCHITECTURE-EXPORT ] [ nagvis-shinken-architecture ] [ CONFIGURATION ] Edit /etc/shinken/external/nagvis/etc/nagvis.ini.php file
[AAAA-MM-DD HH:MM:SS] INFO   : [ arbiter ] [ ARCHITECTURE-EXPORT ] [ nagvis-shinken-architecture ] [ CONFIGURATION ]    - Setting WebUI connection to allow redirection on NagVis maps
[AAAA-MM-DD HH:MM:SS] DEBUG  : [ arbiter ] [ ARCHITECTURE-EXPORT ] [ nagvis-shinken-architecture ] [ CONFIGURATION ]        => "shinken_auth_protocol" parameter set to [ http ]
[AAAA-MM-DD HH:MM:SS] DEBUG  : [ arbiter ] [ ARCHITECTURE-EXPORT ] [ nagvis-shinken-architecture ] [ CONFIGURATION ]        => "shinken_auth_port" parameter set to [ 7767 ]
[AAAA-MM-DD HH:MM:SS] DEBUG  : [ arbiter ] [ ARCHITECTURE-EXPORT ] [ nagvis-shinken-architecture ] [ CONFIGURATION ]        => "shinken_auth_address" parameter set to [ 192.168.1.119 ]
[AAAA-MM-DD HH:MM:SS] DEBUG  : [ arbiter ] [ ARCHITECTURE-EXPORT ] [ nagvis-shinken-architecture ] [ CONFIGURATION ]        => "hosturl" parameter set to [ http://192.168.1.119:7767/detail-by-name/[host_name] ]
[AAAA-MM-DD HH:MM:SS] DEBUG  : [ arbiter ] [ ARCHITECTURE-EXPORT ] [ nagvis-shinken-architecture ] [ CONFIGURATION ]        => "serviceurl" parameter set to [ http://192.168.1.119:7767/detail-by-name/[host_name]/checks/[service_description] ]
[AAAA-MM-DD HH:MM:SS] INFO   : [ arbiter ] [ ARCHITECTURE-EXPORT ] [ nagvis-shinken-architecture ] [ CONFIGURATION ]    - Setting Livestatus connection to get Shinken objects status
[AAAA-MM-DD HH:MM:SS] DEBUG  : [ arbiter ] [ ARCHITECTURE-EXPORT ] [ nagvis-shinken-architecture ] [ CONFIGURATION ]        => "socket" parameter set to [ socket="tcp:192.168.1.119:50000" ]
[AAAA-MM-DD HH:MM:SS] INFO   : [ arbiter ] [ ARCHITECTURE-EXPORT ] [ nagvis-shinken-architecture ] [ CONFIGURATION ] File /etc/shinken/external/nagvis/etc/nagvis.ini.php edited
[AAAA-MM-DD HH:MM:SS] INFO   : [ arbiter ] [ ARCHITECTURE-EXPORT ] [ nagvis ] [ CONFIGURATION ] UPDATING connection between NagVis and Shinken modules
[AAAA-MM-DD HH:MM:SS] INFO   : [ arbiter ] [ ARCHITECTURE-EXPORT ] [ nagvis ] [ CONFIGURATION ] Edit /opt/nagvis/etc/nagvis.ini.php file
[AAAA-MM-DD HH:MM:SS] INFO   : [ arbiter ] [ ARCHITECTURE-EXPORT ] [ nagvis ] [ CONFIGURATION ]    - Setting WebUI connection to allow redirection on NagVis maps
[AAAA-MM-DD HH:MM:SS] DEBUG  : [ arbiter ] [ ARCHITECTURE-EXPORT ] [ nagvis ] [ CONFIGURATION ]        => "shinken_auth_protocol" parameter set to [ http ]
[AAAA-MM-DD HH:MM:SS] DEBUG  : [ arbiter ] [ ARCHITECTURE-EXPORT ] [ nagvis ] [ CONFIGURATION ]        => "shinken_auth_port" parameter set to [ 7767 ]
[AAAA-MM-DD HH:MM:SS] DEBUG  : [ arbiter ] [ ARCHITECTURE-EXPORT ] [ nagvis ] [ CONFIGURATION ]        => "shinken_auth_address" parameter set to [ 192.168.1.119 ]
[AAAA-MM-DD HH:MM:SS] DEBUG  : [ arbiter ] [ ARCHITECTURE-EXPORT ] [ nagvis ] [ CONFIGURATION ]        => "hosturl" parameter set to [ http://192.168.1.119:7767/detail-by-name/[host_name] ]
[AAAA-MM-DD HH:MM:SS] DEBUG  : [ arbiter ] [ ARCHITECTURE-EXPORT ] [ nagvis ] [ CONFIGURATION ]        => "serviceurl" parameter set to [ http://192.168.1.119:7767/detail-by-name/[host_name]/checks/[service_description] ]
[AAAA-MM-DD HH:MM:SS] INFO   : [ arbiter ] [ ARCHITECTURE-EXPORT ] [ nagvis ] [ CONFIGURATION ]    - Setting Livestatus connection to get Shinken objects status
[AAAA-MM-DD HH:MM:SS] DEBUG  : [ arbiter ] [ ARCHITECTURE-EXPORT ] [ nagvis ] [ CONFIGURATION ]        => "socket" parameter set to [ socket="tcp:192.168.1.119:50000" ]
[AAAA-MM-DD HH:MM:SS] INFO   : [ arbiter ] [ ARCHITECTURE-EXPORT ] [ nagvis ] [ CONFIGURATION ] File /opt/nagvis/etc/nagvis.ini.php edited



Si aucune modification n'est attendue, dû à une erreur de configuration, l'architecture-export lira simplement la configuration de NagVis afin d'afficher son état actuel

[AAAA-MM-DD HH:MM:SS] INFO   : [ arbiter ] [ ARCHITECTURE-EXPORT ] [ nagvis-shinken-architecture ] [ CONFIGURATION ] The connection between NagVis and Shinken modules will not be changed
[AAAA-MM-DD HH:MM:SS] INFO   : [ arbiter ] [ ARCHITECTURE-EXPORT ] [ nagvis-shinken-architecture ] [ CONFIGURATION ] Read /etc/shinken/external/nagvis/etc/nagvis.ini.php file
[AAAA-MM-DD HH:MM:SS] INFO   : [ arbiter ] [ ARCHITECTURE-EXPORT ] [ nagvis-shinken-architecture ] [ CONFIGURATION ]    - No WebUI module found, we will keep previous NagVis configuration. Redirection to WebUI on NagVis maps may not work properly
[AAAA-MM-DD HH:MM:SS] DEBUG  : [ arbiter ] [ ARCHITECTURE-EXPORT ] [ nagvis-shinken-architecture ] [ CONFIGURATION ]        => "shinken_auth_protocol" parameter not changed. It is still [ http ]
[AAAA-MM-DD HH:MM:SS] DEBUG  : [ arbiter ] [ ARCHITECTURE-EXPORT ] [ nagvis-shinken-architecture ] [ CONFIGURATION ]        => "shinken_auth_port" parameter not changed. It is still [ 7767 ]
[AAAA-MM-DD HH:MM:SS] DEBUG  : [ arbiter ] [ ARCHITECTURE-EXPORT ] [ nagvis-shinken-architecture ] [ CONFIGURATION ]        => "shinken_auth_address" parameter not changed. It is still [ 192.168.1.119 ]
[AAAA-MM-DD HH:MM:SS] DEBUG  : [ arbiter ] [ ARCHITECTURE-EXPORT ] [ nagvis-shinken-architecture ] [ CONFIGURATION ]        => "hosturl" parameter not changed. It is still [ http://192.168.1.119:7767/detail-by-name/[host_name] ]
[AAAA-MM-DD HH:MM:SS] DEBUG  : [ arbiter ] [ ARCHITECTURE-EXPORT ] [ nagvis-shinken-architecture ] [ CONFIGURATION ]        => "serviceurl" parameter not changed. It is still [ http://192.168.1.119:7767/detail-by-name/[host_name]/checks/[service_description] ]
[AAAA-MM-DD HH:MM:SS] INFO   : [ arbiter ] [ ARCHITECTURE-EXPORT ] [ nagvis-shinken-architecture ] [ CONFIGURATION ]    - No Livestatus module found, we will keep previous NagVis configuration. Status of Shinken elements on NagVis maps may not work properly
[AAAA-MM-DD HH:MM:SS] DEBUG  : [ arbiter ] [ ARCHITECTURE-EXPORT ] [ nagvis-shinken-architecture ] [ CONFIGURATION ]        => "socket" parameter not changed. It is still [ socket="tcp:192.168.1.119:50000" ]
[AAAA-MM-DD HH:MM:SS] INFO   : [ arbiter ] [ ARCHITECTURE-EXPORT ] [ nagvis ] [ CONFIGURATION ] The connection between NagVis and Shinken modules will not be changed
[AAAA-MM-DD HH:MM:SS] INFO   : [ arbiter ] [ ARCHITECTURE-EXPORT ] [ nagvis ] [ CONFIGURATION ] Read /opt/nagvis/etc/nagvis.ini.php file
[AAAA-MM-DD HH:MM:SS] INFO   : [ arbiter ] [ ARCHITECTURE-EXPORT ] [ nagvis ] [ CONFIGURATION ]    - No WebUI module found, we will keep previous NagVis configuration. Redirection to WebUI on NagVis maps may not work properly
[AAAA-MM-DD HH:MM:SS] DEBUG  : [ arbiter ] [ ARCHITECTURE-EXPORT ] [ nagvis ] [ CONFIGURATION ]        => "shinken_auth_protocol" parameter not changed. It is still [ http ]
[AAAA-MM-DD HH:MM:SS] DEBUG  : [ arbiter ] [ ARCHITECTURE-EXPORT ] [ nagvis ] [ CONFIGURATION ]        => "shinken_auth_port" parameter not changed. It is still [ 7767 ]
[AAAA-MM-DD HH:MM:SS] DEBUG  : [ arbiter ] [ ARCHITECTURE-EXPORT ] [ nagvis ] [ CONFIGURATION ]        => "shinken_auth_address" parameter not changed. It is still [ 192.168.1.119 ]
[AAAA-MM-DD HH:MM:SS] DEBUG  : [ arbiter ] [ ARCHITECTURE-EXPORT ] [ nagvis ] [ CONFIGURATION ]        => "hosturl" parameter not changed. It is still [ http://192.168.1.119:7767/detail-by-name/[host_name] ]
[AAAA-MM-DD HH:MM:SS] DEBUG  : [ arbiter ] [ ARCHITECTURE-EXPORT ] [ nagvis ] [ CONFIGURATION ]        => "serviceurl" parameter not changed. It is still [ http://192.168.1.119:7767/detail-by-name/[host_name]/checks/[service_description] ]
[AAAA-MM-DD HH:MM:SS] INFO   : [ arbiter ] [ ARCHITECTURE-EXPORT ] [ nagvis ] [ CONFIGURATION ]    - No Livestatus module found, we will keep previous NagVis configuration. Status of Shinken elements on NagVis maps may not work properly
[AAAA-MM-DD HH:MM:SS] DEBUG  : [ arbiter ] [ ARCHITECTURE-EXPORT ] [ nagvis ] [ CONFIGURATION ]        => "socket" parameter not changed. It is still [ socket="tcp:192.168.1.119:50000" ]



La modification/lecture de la configuration de NagVis est visible 2 fois. Ceci est dû au fait que nous fournissons deux installations NagVis distincts : 

nagvis-shinken-architecture, qui est celui sur lequel nous mettons à disposition des cartes générées automatiquement

nagvis, qui lui ne contient aucune carte générée par Shinken