Architecture

Architecture

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.

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 Instances:

  • Agents
  • Modules
  • Alerts
  • Policies

On the Metaconsole:

  • The Metaconsole configuration:
  • Components
  • Reports* and the report templates
  • Network maps*
  • Visual maps*
  • Netflow filters

On both:

  • Users and profiles
  • Groups
  • Templates, actions and alert commands
  • Tags
  • Categories

* Though these items are stored in the Metaconsole, they are configurations used to view Instance data, therefore they are useless on their own.

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).

Go back to Pandora FMS documentation index