Architecture and Synchronization
The Metaconsole architecture is made up by a single central node, the Metaconsole along with as many server nodes as desired, the Instances.
Instances are normal Pandora FMS installations. They consist of a web console in the front end and a server in the back end that processes the received data, performs remote checks,etc.
From version 6.0 onwards, the Metaconsole has been modified and it currently has its own server, for previous versions the Metaconsole does not have its own server.
Version NG 755 or earlier: you will need to configure the use of the Command Center, where all the relevant information is available.
From Pandora FMS version 756, the synchronization system for environments with centralized mode has been redesigned from scratch, making it faster and more efficient, since the changes will be replicated to the nodes automatically without the need for manual synchronization, as it was the case up to now.
This change deems the previous system outdated, so in environments where it was active, it will have to go through the previous automatic merging system to use the new centralization system and be able to guarantee data integrity.
When updating, all already centralized Metaconsole environments will be forced to go through the new Command Center to be able to be centralized again correctly.
Where does it store data?
Some data can be found on the Instances, others on the Metaconsole, and others in both places. They need to be synchronized to work properly.
On the Metaconsole:
- The Metaconsole configuration.
- Reports1) and the report templates.
- Network maps.2)
- Visual maps.3)
- NetFlow filters.
- Users and profiles.
- Templates, actions and alert commands.
How is information retrieved and modified?
The Metaconsole obtains and modifies Instance information in two different ways:
- Active: Access to the instance Database or API remotely from the Metaconsole (this is the case for agents, modules, alerts, etc.).
- Passive: Replicates data from instances to the Metaconsole Database (this is the case for events).