Pandora: Metaconsole: Documentation en: Arquitecture

From Pandora FMS Wiki
Jump to: navigation, search

Go back to Pandora FMS documentation index

1 Architecture

The Metaconsole architecture is composed by a single central node: The Metaconsole along with as many server nodes as you want, which here we call Instances.

Instances are normal installations of Pandora FMS. They consist of a web console in the front end and a server in the back end that processes the data received, performs remote checks,etc.

From version 6.0 onward, the Metaconsole has been changed and now has its own server, for previous versions the Metaconsole doesn't have its own server.

1.1 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 between themselves to work properly.

On Instances:

  • Agents
  • Modules
  • Alerts
  • Policies

On the Metaconsole:

  • The Metaconsole configuration:
  • Components
  • Reports* and the template reports
  • Network maps*
  • Visual maps*
  • Netflow filters

In both:

  • Users and profilesThe userLos usuarios y perfiles
  • Groups
  • Templates, actions and alert commands
  • Tags
  • Categories

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

1.2 How is information obtained and modified?

The Metaconsole obtains and modifies the Instances' information in two different ways:

  • Active: Accesses the instances' Database or API remotelt from the Metaconsole (this is the case for agents,modules, alerts, etc).

Metaconsola Arquitecture Active.png

  • Passive: replicates data from instances to the Metaconsoloe Database (this is the case for events).

Metaconsola Arquitecture Passive.png

2 Synchronization

The metaconsole has tools for element synchronization, such as the synchronization of users and groups, which are fundamental for the correct management of the Instances. Synchronization is based on passing all the information created in the metaconsole to the different Instances in order to manage all possible information of each instance from the metaconsole.

For example, a user created in an Instance, but not in the metaconsole, cannot be managed from the metaconsole. On the other hand, if we have a user created in the metaconsole, and we synchronize the users, this user will be in the Instances and we will be able to manage it from the metaconsole.

Metaconsola Users Sync.png

3 Propagation

The Meta Console has tools for the propagation of elements, such as the propagation of components or the movement of agents between Instances (or nodes). Unlike synchronization, it is not a fundamental tool for the optimal functioning of the Meta Console, it only facilitates the availability of data in the Instances, something that is necessary if, for example, we use policies that are applied in different instances (or nodes).

For example, we may want to move an agent from Instance A to Instance B to balance the load of the instances, through the set of these tools we could easily achieve this.

Metaconsola Agents Prop.png

Return to the Pandora FMS documentation index