Pandora: Metaconsole: Documentation en: Introduction
Go back to Pandora FMS documentation index
|
|
This is an advanced topic. You should already be familiar with Pandora FMS before attempting to deploy a Metaconsole. For more information contact us at [email protected] |
|
Contents
1 Introduction
The Metaconsole is a console where you can visualize, synchronize and manage in a unified way different Pandora FMS monitoring systems, from now on Instances (nodes), exclusive of the Enterprise version. Thanks to this console we can monitor hundreds of thousands of different devices in a centralized way, without having to look at each Instance (node) individually.
The metaconsole offers a multitenant service, where it can be the access point for a user that belongs to a company or where a single console can offer service to different companies, and within each company to different users of the same. Below is a schematic of the architecture of the meta console where we can see its horizontal scalability, where each instance has its own database to operate.
It is a very complex environment, which incorporates the necessary functions to manage the different Instances. The metaconsole is designed not to operate at a low level as the Instances, but to manage in a centralized way all the infrastructure of all the Instances.
Thanks to this console we can observe a lot of information through different functions such as the generation of reports or visual consoles with elements of different Instances, as well as the synchronization of events. In addition, we can manage the different Instances with the creation of new agents, their distribution, management of alert templates, policies and other functions.
2 Comparative
If you knew Pandora FMS before version 5.0, then you know that the Metaconsole concept already exist
In this section, we are going to analyze the differences between the current Metaconsole and the old one,and also the problems solved and the improvements proposed.
2.1 Before Version 5.0
Before version 5.0, a normal installation (Console+Server) of Pandora FMS could also work, as Metaconsole.
2.1.1 Communication
The communication between the Metaconsole and the instances was unidirectional. The Metaconsole connected with the instance data base and Managed all the data in memory.
It did not store almost nothing in its own database.
2.1.2 Synchronization
Synchronization was done between the instances. For example:
Lets suppose that we want to configure some alert templates so as all the instances would have them.
We should enter in one of the instances, configure them, go back to the Metaconsole and synchronize the templates of that instance with the other ones.
2.1.3 Problems
The Metaconsole was very inefficient because of its not centralized architecture. A lot of connections were done to different databases and the user experience was poor.
The available options were insufficient to get the wanted control of the instance environments without exit from the Metaconsole.
Summarizing, the Metaconsole was slow in case it had a bit of load and the user was very limited by its options.
2.2 From Version 5.0
The Metaconsole from version 5.0 is an special environment completely independent and incompatible with the console.
2.2.1 Communication
The communication between the Metaconsole and the instances is bi-directional. The Metaconsole connect with the instance database and the instances replicate part of their data to the Metaconsole database.
Other data, such as groups, alert templates, tags... are stored in the Metaconsole.
2.2.2 Synchronization
The synchronization is done in a one way: From the Metaconsole to the instances.
For example:
Lets suppose that we want to configure some alert templates for the ones that have several or all instances. Without exit from the metaconsole we could configure the templates and synchronize them with the instances that we want.
2.2.3 Improvements
The Metaconsole from version 5.0 is a much more centralized, quick, and flexible tool than the previous version. It also includes much more views and features, and also improvements in the ones that previously exist. It does not manage all data in memory, storing part of the information, improving this way the user experience.
2.3 Summary table
In the following table you can see the differences between the old Metaconsole features and the new ones.
| Before version 5.0 | From version 5.0 | |
|---|---|---|
| The metaconsole can work as an instance |  |
 |
| Synchronization | ||
| Communication | ||
| Instance configuration | |
|
| User panel | |
|
| Tactic view | ||
| Agent browser | |
|
| Group view | |
|
| Event visor | (Data in Instances) |
(Data in the Metaconsole) |
| Tree view | |
|
| Alert view | |
|
| Module view | |
|
| Network map | |
|
| Traffic monitoring (Netflow) | |
|
| Synchronization tools |
|
|
| Move agents between instances | |
|
| Report templates | |
|
| Editors |
|
|
| Apply/Policy queue | |
|
