Pandora: Documentation en: Export Server
1 Export Server
The Pandora FMS Enterprise Version implements a data scaling device which allows you to conduct a virtually distributed implementation, able to monitor an unlimited number of information by utilizing an export server as long as you design it properly and break it up into different information profiles.
The main idea consists of creating a hierarchical structure which distributes the information from down to top, the top point being the more global one, which only collects an extract of basic information of Pandora FMS installations on the lowest level, instead of collecting a bigger number of information. This method allows to have a 'filtered' view and more information density for the highest Pandora FMS installation.
The server which exports the data is hierarchically below the server which receives this information. You're able to use this technology to conduct a reply of all data reported by a server in a different sketch of the filtered view, although it could seriously affect the server's performance.
Each independent installation of Pandora FMS was designed to export those data to one or several servers which can be selected by the administrator.
It's also possible to export data that originates from modules, so a hierarchically higher Pandora FMS installation is able to receive important data.
The processing of events, its viewing, reports, users and permissions will be different for each Pandora FMS installation. There will be installations totally different at all purposes. The higher request could not be executed in real-time data refresh petitions, so these data is passively obtained. There is no access to the monitored elements of lower petitions. The access security, the information partition and access to privileged information is guaranteed by the architectural design.
The server which receives the data receives it by an XML file, similar to the ones agents would generate, in a way that they only require to have a data server available. The higher server (the one which receives the data) only receives data. It doesn't receive events and can't reuse the alerts defined on the server which receives the data first. It should define its own alerts and reports, customized graphs, etc.
In order to export module data, the first step is to define a scaling server, containing different configuration options which would allow to export a link between a server (or client) which exports and a server which imports.
Please click on 'Administration' -> 'Manage Servers' -> 'Export Targets' and on the 'Create' button in order to create a Target Server.
1.2 Adding a Target Server
Once you've clicked on the 'Create' button, a window like the one shown on the picture below is going to appear.
The configurable fields pertaining to this particular feature are the following:
The Pandora FMS server's name.
The combo intended to pick the export server's petition which is going to be used to export the data.
The prefix used to add to the agent's name which sends the data, e.g. if the data of an agent named 'Farscape' is resent and its prefix in the export server is 'EU01', the resent agent's data is going to show up with an agent name 'EUO1-Farscape' on the destination server. This allows you to learn the data's origin in case of a server we receive different sources of information from, coming from different Pandora FMS servers, with which we would force a name duplicity. The server will always add the '_' character after the prefix, so it would be empty. The '_' character is always going to be put in front of the agent's name on the destination server.
It defines the time interval and how often (in seconds) you intend to send the data which are considered unresolved. The data is always going to be collected from the original source. If an agent collects data every 300 seconds and there are a 1000 seconds configured here, means that the server is going to send what has been collected until this moment. In this case, this would mean to receive three packages by this agent with an interval of '300'.
It's the remote target directory in which it's going to deposit the data. It's used for SSH or FTP only.
The data-server address which is going to receive the data.
The file transfer mode. You're able to pick the following modes:
- Local: The data-receiving server is on the same machine as the export server.
- SSH: The transfer address if the transference is conducted by SSH. In this case it's necessary to copy the certificate of the server which exports the data to the server which receives it.
- FTP: The transfer is conducted by using the FTP protocol.
- Tentacle: The transfer is conducted by using the Tentacle protocol (recommended).
The user for FTP.
The user's password for FTP.
The port used in the file transfers. The default port for the Tentacle protocol is '41121'.
The field for additional options like the ones Tentacle requires to work with certificates.
1.3 Editing a Target Server
In order to edit a target server, please click on the target server's name or on the wrench-shaped icon as shown on the picture below.
1.4 Deleting a Target Server
Please click on the trash icon which is located on the right side of the target server's name in order to delete it.
1.5 Linking a Target Server to a Module
In order to scale the information, you're required to select the modules one by one which are able to send the information to a higher instance. In order to do this, the Pandora FMS console's module editor implements an option which allows you to assign one export server for each type of data. To do this, go to the configuration of those modules we want to send information about. Within the advanced options we will choose the necessary export target.
Please click on the 'Update' button so that Pandora FMS is able to begin the data-exporting process to the afore selected server.
Go back to Pandora FMS Documentation Index