サーバアーキテクチャ (バージョン 784)

Pandora FMS ドキュメント一覧に戻る

In the latest change in architecture, which moved from threads to processes, it became clear that there was excessive consumption and complexity in optimizing the environment due to the existence of too many server subtypes.

アーキテクチャ の最新の変更にて、スレッドからプロセスに移行しました。サーバのサブタイプの数が多すぎることにより環境の最適化に過剰な消費と複雑さが生じることが明らかになりました。

Servers are integrated into a single application, called Pandora Server as an ensemble, which is a multithreaded application that runs different instances or specialized Pandora FMS servers at the same time. For version 783 and earlier, the following servers were available:

サーバは、Pandora Server と呼ばれる単一のアプリケーションに統合され、一連のものとして機能します。これは、異なるインスタンスまたは専用の Pandora FMS サーバを同時に実行するマルチスレッドアプリケーションです。バージョン 783 以前では、以下のサーバーが利用可能でした。

• Data Server.
• SNMP Console.
• Syslog Server.
• Export Server (rarely used).
• Sync Server (few use).
• Discovery Server.
• WEB Server.
• Network Server.
• WMI Server.
• Plugins Server.
• Inventory Server.
• ICMP Server.
• SNMP Server (different from SNMP traps).
• Event Server.
• Log Server.
• SIEM Server.
• NetFlow Server (including sFlow).
• NCM Server.
• Policy Manager Server.
• WUX Server.
• MADE Server.

• データサーバ
• SNMP コンソール
• Syslog サーバ
• エクスポートサーバ (ほとんど使用されません)
• 同期サーバ（使用は少ない）
• 自動検出サーバ
• ウェブサーバ
• ネットワークサーバ
• WMI サーバ
• プラグインサーバ
• インベントリサーバ
• ICMP サーバ
• SNMP サーバ (SNMP トラップは別)
• イベントサーバ
• ログサーバ
• SIEM サーバ
• NetFlow サーバ (sFlow を含む)
• NCM サーバ
• ポリシー管理サーバ
• WUM サーバ
• MADE サーバ

Given this overview, and in an environment with half of the servers started, high memory usage was detected without having actually started working.

この概要を踏まえ、サーバの半数が起動している環境では、実際に処理を行っていないにもかかわらず、高いメモリ使用量となっていました。

In version 784, the different servers have been grouped into a smaller group, which means that a producer may generate different types of tasks, e.g., a ping and a WMI check, which are now processed by the same user. This user will execute one task for WMI and another for PING, essentially doing the same thing as always.

It takes on the tasks of the following servers:

• Network Server.
• WMI Server.
• MADE Server.
• WEB Server.

It handles the tasks of the following servers:

• Plugin Server.
• NCM Server
• Export Server (disabled by default).
• Inventory Server.

It manages the workloads of the ICMP Server and SNMP Server.

• Policy Manager (it depends on the Master server of a node).
• Migration server (it depends on the Master server of a Command Center ).
• Autoprovision server (it depends on the Master server of a Command Center).
• Sync server (disabled by default).

Servers enabled by default:

• Data Server.
• Heavy Server.
• Network Server.
• Discovery Server.
• Network High Performance Server.

Servers disabled by default:

• MADE Server.
• SNMP Trap Server.
• Mainframe Server.
• NetFlow Server.
• Syslog Server.
• WUX Server.
• SIEM Server.
• SIEM Server.
• Event Server.
• Log Server.
• Alert Server.

The main configuration of Pandora FMS Server is located in file pandora_server.conf, in the default path /etc/pandora.

Starting with version 784, two main new tokens (and their thread configurations) are added:

• heavyserver.
• networkhpserver.

The following tokens were removed:

In version 784 there is a new category in the deletion parameters that especially affects data with interval times lower than 300 seconds. By default, this type of data cannot be stored for more than a week, and is moved to history from that point on.

This new data compression is used when transferring data to the history database, so that regardless of the data, no more than X samples per hour are stored in the history database (e.g., from 12, which is normal, it can change to 5 by default).

Default setting: this type of compression is not used.

If used, the default value of 5 samples per hour will be used. The general configuration control does not allow values lower than 1 or higher than 12. Compaction is not performed in cases where the number of samples is lower than the established value.

Pandora FMS ドキュメント一覧に戻る