Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
en:documentation:06_metaconsole:04_command [2021/08/20 00:21]
jimmy.olano [Stage 2: Event updating]
en:documentation:06_metaconsole:04_command [2021/11/05 12:05] (current)
Line 1: Line 1:
-====== COMMAND CENTER ======+====== Command Center ======
  
 {{indexmenu_n>3}} {{indexmenu_n>3}}
  
 [[:en:documentation:start|Go back to Pandora FMS documentation index]] [[:en:documentation:start|Go back to Pandora FMS documentation index]]
 +
  
 ===== Command Center ===== ===== Command Center =====
Line 180: Line 181:
 ==== Environment already centralized through Command Center ==== ==== Environment already centralized through Command Center ====
  
-Once stage 1 is finished, the environment will be considered centralized, and from there you will be able to manage everything from the Metaconsole. Element synchronization has also been changed, now the ''pandora_ha'' process of each node is in charge of synchronizing its database with that of the Metaconsole ().+Once stage 1 is finished, the environment will be considered centralized, and from there you will be able to manage everything from the Metaconsole. Element synchronization has also been changed, now the ''pandora_ha'' process of each node is in charge of synchronizing its database with that of the Metaconsole.
  
 When you make a change in the Metaconsole (for example, create a user) this queues the necessary queries to the database for the nodes (''INSERTS'', ''UPDATES'', etc.) which ''pandora_ha'' reads in an orderly manner and executes in each server_threshold. This ensures that if a server is down for a while, when it is started again it can catch up correctly. When you make a change in the Metaconsole (for example, create a user) this queues the necessary queries to the database for the nodes (''INSERTS'', ''UPDATES'', etc.) which ''pandora_ha'' reads in an orderly manner and executes in each server_threshold. This ensures that if a server is down for a while, when it is started again it can catch up correctly.
ºº