最大 30 日間の範囲の過去データに基づいて統計的なデータ予測を実装する AI コンポーネントです。これにより、10～15 分間隔でデータ項目の値を予測し、特定のデータセットにおいて履歴から異常を示しているかどうかを知ることができます。基本的には週次で動的なベースラインを構築します。
最大 30 日間の範囲の過去データに基づいて統計的なデータ予測を実装する AI コンポーネントです。これにより、10～15 分間隔でデータ項目の値を予測し、特定のデータセットにおいて履歴から異常を示しているかどうかを知ることができます。基本的には週次で動的なベースラインを構築します。
+
+
<wrap #ks1_1_8 />
=== ウェブサーバ ===
=== ウェブサーバ ===
行 119:
行 147:
高度な戦略を使用して ICMP チェック (ping) を実行し、事前に検証された OID (**O**bject **ID**entifier) で動作するため、高いパフォーマンスを発揮します。
高度な戦略を使用して ICMP チェック (ping) を実行し、事前に検証された OID (**O**bject **ID**entifier) で動作するため、高いパフォーマンスを発揮します。
+
+
<wrap #ks1_1_13 />
=== サテライトサーバ ===
=== サテライトサーバ ===
-
This component is installed separately in Pandora FMS main server. It forwards data files from [[http://:en:documentation:01_understanding:03_glossary#software_agent|software agents]] to the main server, acting as agent proxy in distributed topologies. It sends monitoring data as XMLs over a tentacle connection, so no database connection is required.
+
It is installed separately from the main Pandora FMS server and allows the forwarding of data files from the [[:en:documentation:pandorafms:introduction:03_glossary#agente_software|Software Agents]] to the main server, acting as agent proxy in [[:en:documentation:pandorafms:complex_environments_and_optimization:05_satellite|distributed topologies]]. It sends the monitoring data as XML files through a Tentacle connection, so it does not require a connection to the database.
-
このコンポーネントは、Pandora FMS メインサーバとは別にインストールされます。 データファイルを [[:ja:documentation:01_ Understanding:03_glossary#ソフトウエアエージェント|ソフトウエアエージェント]] からメインサーバに転送し、分散トポロジでエージェントプロキシとして機能します。tentacle 接続を介して監視データを XML として送信するため、データベース接続は必要ありません。
+
このコンポーネントは、Pandora FMS メインサーバとは別にインストールされます。 データファイルを [[:ja:documentation:pandorafms:introduction:03_glossary#ソフトウエアエージェント|ソフトウエアエージェント]] からメインサーバに転送し、[[:ja:documentation:pandorafms:complex_environments_and_optimization:05_satellite|分散トポロジ]]でエージェントプロキシとして機能します。tentacle 接続を介して監視データを XML として送信するため、データベース接続は必要ありません。
Combined with the [[:en:documentation:pandorafms:monitoring:13_user_monitorization|Selenium Grid]] allows complex web transactions to be carried out in a distributed manner. These transactions are executed in a real browser, their output is captured and processed for step-by-step viewing, including error traps and detailed statistics.
-
Combined with the [[http://:en:documentation:03_monitoring:13_user_monitorization|Selenium Grid]], itallows complex WEB transactions to be carried out in a distributed manner. These transactions are executed in a real browser, and their output is captured and processed to display it step by step, including error screenshots, as well as detailed statistics.
It allows analyzing the **syslog** of the machine where it is located, analyzing its content and storing the references in the corresponding [[:en:documentation:pandorafms:monitoring:09_log_monitoring|OpenSearch server]].
It allows analyzing the **syslog** of the machine where it is located, analyzing its content and storing the references in the corresponding [[:en:documentation:pandorafms:monitoring:09_log_monitoring|OpenSearch server]].
行 144:
行 170:
=== ログサーバ ===
=== ログサーバ ===
-
{{:wiki:icono-modulo-enterprise.png |Enterprise version.}}It allows you to correlate [[:en:documentation:pandorafms:management_and_operation:01_alerts#creating_correlation_alerts|logs and run your alerts]].
+
It allows you to correlate [[:en:documentation:pandorafms:management_and_operation:01_alerts#ks12_1|logs and run your alerts]].
* **Reporting duality:** Additionally, you may configure agents to report to two different Pandora FMS servers, although they can only be managed by one of them.
+
* **Reporting duality**: Additionally, you can configure Agents to report to two different Pandora FMS servers, although it can only be managed by one of them.
-
* **Fragmented management:** It is pretty useful if you are required to **delegate the administration of part of the equipment** to different personnel with different access levels. This is more of a management issue rather than an architectural problem. It can be solved by the [[:en:documentation:04_using:11_managing_and_administration|assigned permissions on policies]].
+
* **Fragmented management**: It is necessary to **delegate the administration of part of the teams** to different personnel, with different accesses. This, more than an architecture problem, is a management problem. It is solved with [[:en:documentation:pandorafms:management_and_operation:11_managing_and_administration#acl_system_enterprise|assigned permissions on policies]].
* **Large-Volume Network:** Consisting of thousands of network testing processes which must be distributed in different 'remote monitoring probes'. Given their large numbers (over 50,000), they cannot be centralized into a single server. To that end, use servers in broker mode that distribute the remote check load.
* **Large-Volume Network:** Consisting of thousands of network testing processes which must be distributed in different 'remote monitoring probes'. Given their large numbers (over 50,000), they cannot be centralized into a single server. To that end, use servers in broker mode that distribute the remote check load.
-
* **Redundant servers**: For security reasons, in case primary hardware fails, a [[http://:en:documentation:05_big_environments:06_ha|server in HA mode]] may automatically relocate and delegate the monitoring workload.
+
* **Redundant servers**: For safety, should the primary hardware fail, [[:en:documentation:pandorafms:complex_environments_and_optimization:06_ha|a server in HA mode]] can automatically relocate and delegate the monitoring workload.