The monitoring carried out by Pandora FMS is classified into Logical Agents, which always belong to a Group. These are equivalent to each of the different computers, devices, websites or applications that are subject to monitoring.
These Agents defined in the Pandora FMS Console can present local data collected through a EndPoint, remote data collected through network checks, or both types of data.
* **Agent-based monitoring** consists of installing a small program (EndPoint) that remains running on the system, obtaining data **locally**, by executing commands and/or scripts ( scripts).
+
* **Remote monitoring** consists of using the network to perform remote checks on the systems, without the need to install any additional component on the equipment to be monitored.
**Main fields of the editing interface in normal view**
**通常の主な編集インターフェイスフィールド**
**通常の主な編集インターフェイスフィールド**
-
* **Alias**: For the proper functioning of all the functions that Pandora FMS performs through agents and modules, avoid the use of the following characters ''/'', ''\'', ''|'', ''%'', ''#'', ''&'' and ''$'' for the name of the agent or module. If these agents contain such characters, they can create confusion with the use of system paths or execution of other commands, causing errors on the server.
+
* <wrap :en>**Alias**</wrap>: For proper operation of all functions that Pandora FMS performs with agents and modules, avoid the use of the following characters ''/'', ''\'', ''|'', ''%'', ''#'', ''&'' and ''$ ''within the agent or module name. If these agents contain such characters, they may be misunderstood for system paths or command execution, generating server errors.
-
* **Server**: Server that will execute the checks configured in agent monitoring, special parameter in case of having configured [[:en:documentation:pandorafms:complex_environments_and_optimization:06_ha|HA]] in your installation.
+
* The <wrap :en>**Server**</wrap> field allows you to indicate one of these options:
-
* **Primary group**: It allows you to assign a group to the agent. Clicking on the group icon will lead you to the assigned group tactical view.
+
-
* **IP address**: It allows you to assign an IP address to the agent. With the **Check unique IP** button you may check whether the IP address entered is free, if it is already in the list of saved addresses for that agent (it has a deletion option) **or if it is in use by another agent**. In case it is used by another agent, when saving the modifications, it will warn about it and it will ask for a confirmation before registering this data. In the [[:en:documentation:pandorafms:management_and_operation:12_console_setup#general_setup|General Configuration]] it could be configured so that the **Check unique IP** button is automatically used for editing all the agents.
+
- <wrap :en>**None**</wrap>: No server will run agent modules.
+
- <wrap :en>**Autobalance**</wrap>: Any available server will run agent modules.
+
- <wrap :en>**Server name**</wrap>: Select a specific server to run the agent modules.
+
+
* <wrap :en>**Auto HA**</wrap>: If enabled, agent modules will be run by another server in case the assigned server is not available (enabled by default). **//It applies only when a specific server is chosen for module execution//**.
+
* <wrap :en>**Primary group**</wrap>: It allows you to assign a group to the agent. By clicking on the group icon you may access the tactical view of the assigned group.
+
* <wrap :en>**IP address**</wrap>: It allows you to assign an IP address to the agent. By means of the <wrap :en>**Check unique IP**</wrap> button, you may check whether the IP address entered is free, if it is already in the list of addresses saved for that agent (it has a deletion option) **or whether it is in use by another agent**. In case it is in use by another agent, a warning will be displayed when saving the editing and a confirmation will be requested before recording the data. In the [[:en:documentation:pandorafms:management_and_operation:12_console_setup#general_setup|General Configuration]], it may be configured so that the <wrap :en>**Check unique IP**</wrap> button is automatically used for editing all agents.
* **IP アドレス(IP address)**: これにより、エージェントに IP アドレスを割り当てることができます。 **ユニーク IP 確認** ボタンを使用すると、入力した IP アドレスが空いているかどうか、そのエージェントの保存済みアドレスのリストに既に存在しているかどうか (削除オプションがあります)、または他のエージェントによって使用されているかどうかを確認できます。別のエージェントによって使用されている場合、変更を保存するときに警告が表示され、このデータを登録する前に確認が求められます。 [[:ja:documentation:pandorafms:management_and_operation:12_console_setup#一般設定|一般設定]] では、すべてのエージェントの編集において **ユニーク IP 確認** ボタンが自動的に使用されるように設定できます。
* **IP アドレス(IP address)**: これにより、エージェントに IP アドレスを割り当てることができます。 **ユニーク IP 確認** ボタンを使用すると、入力した IP アドレスが空いているかどうか、そのエージェントの保存済みアドレスのリストに既に存在しているかどうか (削除オプションがあります)、または他のエージェントによって使用されているかどうかを確認できます。別のエージェントによって使用されている場合、変更を保存するときに警告が表示され、このデータを登録する前に確認が求められます。 [[:ja:documentation:pandorafms:management_and_operation:12_console_setup#一般設定|一般設定]] では、すべてのエージェントの編集において **ユニーク IP 確認** ボタンが自動的に使用されるように設定できます。
行 62:
行 78:
**高度な編集インターフェイスフィールド**
**高度な編集インターフェイスフィールド**
-
* **Secondary groups**: Optional parameter so that an agent can belong to more than one group (secondary groups).
+
* <wrap :en>**Secondary groups**</wrap>: Optional parameter for an agent to belong to more than one group (secondary groups).
-
* **Cascade protection services**: To prevent a flood of cascading alerts. You may choose an agent or an agent module. In the first case, when the chosen agent is critical, the agent will not generate alerts; in the second case, only when the specified module is critical, the agent will not generate alerts.
+
* <wrap :en>**Cascade protection services**</wrap>: To avoid an avalanche of cascading alerts. You may choose an agent or an agent module. In the first case, when the chosen agent is in critical, the agent will not generate alerts; in the second case, only when the specified module is in critical, the agent will not generate alerts.
+
* <wrap :en>**Ignore unknown**</wrap>: This disables calculation of the unknown state in the agent and in any of its modules, so the transition to unknown will never be performed. The state it reflects is the last known state.
Three work modes can be selected for **Module definition**:
+
Three working modes may be selected for defining modules (<wrap :en>**Module definition**</wrap>):
**モジュール定義**では 3 つの作業モードを選択できます。
**モジュール定義**では 3 つの作業モードを選択できます。
-
* **Learning mode**: Default mode, if an XML arrives with new modules, they will be created automatically; it is a learning behavior.
+
* <wrap :en>**Learning mode**</wrap>: Default mode, if an XML arrives with new modules, they will be created automatically; it is a learning behavior.
-
* **Normal mode**: If an XML arrives with new modules, they will only be created if they were previously declared in the Console.
+
* <wrap :en>**Normal mode**</wrap>: If an XML with new modules arrives, they will only be created if they are previously declared in the Console.
-
* **Autodisable mode**: It is the same as the learning mode, but if all modules go to unknown, the agent will be disabled until new information arrives.
+
* <wrap :en>**Autodisable mode**</wrap>: It is the same as the learning mode, but if all modules are set to unknown, the agent will be disabled until new information arrives.
* **学習モード(Learning mode):** 新たなモジュールを含む XML を受け取った場合、モジュールを自動的に作成します。(デフォルト)
* **学習モード(Learning mode):** 新たなモジュールを含む XML を受け取った場合、モジュールを自動的に作成します。(デフォルト)
* **通常モード(Normal mode):** 新たなモジュールを含む XML を受け取った場合、すでにコンソールに設定が無ければ作成しません。
* **通常モード(Normal mode):** 新たなモジュールを含む XML を受け取った場合、すでにコンソールに設定が無ければ作成しません。
This screen offers a large amount of information regarding the agent, with the possibility of forcing the execution of remote checks and refreshing data. At the top it shows a summary with various agent data.
* **List of modules**: belonging to the agent and their respective states (only initialized modules).
+
* Full list of [[:en:documentation:pandorafms:management_and_operation:01_alerts|alerts]] from the agent, with the option to select one or more alerts and validate them.
+
* Status of log sources as configured in [[:en:documentation:pandorafms:monitoring:09_log_monitoring|Log Collection]].
+
* List with the last [[:en:documentation:pandorafms:management_and_operation:02_events|events]] of the agent, with the option to show only the events of the last 24 hours.
Using the [[:en:documentation:02_installation:03_interface#favorite|favorites system]] you may add any agent to a custom list for each user. Click on the star button right next to the agent's name in your main view.
+
Using the [[:en:documentation:pandorafms:installation:03_interface#favorite|favorite system]] you can add any agent to a custom list for each user. Click the star button right next to the agent's name in your main view.
You may add (or remove) as many agents as you need, all of them will always be visible in the **Agents** section of the **Favorite** menu (**Operation** section).
+
You can add (or remove) as many agents as you need, all of them will always be visible in the **Agents** section of the **Favorite** menu (**Operation** section).
Modules have one of several data types: boolean, numeric or alphanumeric, [[:en:documentation:pandorafms:installation:05_configuration_agents#module_type|among others.]]
-
**Full list of [[:en:documentation:04_using:01_alerts|alert]]s**of the agent, with the option to select one or several alerts and validate them through the **Validate** button:
List with the latest [[https://:en:documentation:04_using:02_events|events]] for this agent (**Latest events for this agent**), with the option to show only the events of the last 24 hours (**Show all Events 24h**):
このエージェントの最新の [[:ja:documentation:04_using:02_events|イベント]] を一覧表示します(**このエージェントの最新のイベント(Latest events for this agent)**)。過去 24 時間のイベントのみを表示するオプションがあります (**24 時間以内の全イベント表示(Show all Events 24h)**):
* **WMI モジュール(WMI module):** これは、Windows システムに対して、インストールされているサービスのリストや現在の CPU 負荷の取得などができるリモート監視モジュールです。 この種の監視についてもっと知りたい場合は、[[ja:documentation:03_monitoring:03_remote_monitoring#WMI_.E3.81.A7.E3.81.AE.E3.83.AA.E3.83.A2.E3.83.BC.E3.83.88_Windows_.E3.83.A2.E3.83.8B.E3.82.BF.E3.83.AA.E3.83.B3.E3.82.B0|こちら]] を参照してください。
+
-
* **予測モジュール(Prediction module):** これは、監視対象サーバーの平均 CPU 使用率や接続待ち時間の合計など、他の "基本" モジュールからのデータを参照してさまざまな算術演算を実行する予測監視モジュールです。 この種の監視についてもっと知るためには、[[ja:documentation:03_monitoring:10_other_monitoring|こちら]] を参照してください。
+
-
* **ウェブサーバモジュール(Webserver module):** これは、たとえば Web サイトが停止しているかどうか、または特定の単語が含まれているかどうかを確認するなど、Web サイトの状態をチェックしてデータを取得する Web 監視です。この種の監視についてもっと知りたい場合は、[[ja:documentation:03_monitoring:06_web_monitoring|こちら]] を参照してください。
+
-
* **ウェブ分析モジュール(Web analysis module):** これは、Web サイトの参照、資格情報の導入、フォームへの準拠など、ユーザの Web 参照のシミュレーションが実行できる Web 監視です。 この種の監視についてもっと知りたい場合は、[[ja:documentation:03_monitoring:13_user_monitorization|こちら]] を参照してください。
+
==== 状態監視 ====
==== 状態監視 ====
行 350:
行 381:
==== 基本オプション ====
==== 基本オプション ====
-
<WRAP center round important 60%>\\
+
<WRAP center round important 90%>
-
Always keep in mind that this interface is used by [[:en:documentation:03_monitoring:01_intro_monitoring#monitoring_by_software_agent_vs._remote_monitoring|both local monitoring and remote monitoring]] and presents parameters that are valid in one or the other domain. For example, the **Timeout** and **Retries** parameters are not useful in local monitoring (local checks) but are important in remote monitoring.\\
+
-
</WRAP>\\
+
-
<WRAP center round important 60%>\\
+
It must always be kept in mind that this interface is used both by [[#ks2_1|local monitoring as well as by remote monitoring]] and parameters that are valid in one or another area are presented. For example, the parameters **Timeout** and **Retries** (Retries) are useless in local monitoring (local checks) but are important in remote monitoring.
* **Using module component**: When using a module component, it will be automatically populated with parameter values needed to perform monitoring, this token appears in all module types except for prediction modules.
* **Using module component**: When using a module component, it will be automatically populated with parameter values needed to perform monitoring, this token appears in all module types except for prediction modules.
行 364:
行 397:
* **Disable**: It allows you to disable the module.
* **Disable**: It allows you to disable the module.
* **Module group**: It allows you to assign the module to a defined module group.
* **Module group**: It allows you to assign the module to a defined module group.
-
* **Type**: [[:en:documentation:03_monitoring:02_operations#modules_in_agents_and_software_agents|Module type]] depending on the type of data returned. By selecting **Using module component** the data type will be chosen automatically.
+
* **Type**: [[:en:documentation:pandorafms:monitoring:02_operations#ks1_2|Type of module]] depending on the type of data returned. By selecting **Using module component** the data type will be chosen automatically.
* **Warning threshold** and **Critical threshold**: Thresholds that when reached by the returned value change the status of the module to **warning** status or **critical** status. You may use the **Inverse interval** option to define that the warning/critical status //is any value outside this range//.
* **Warning threshold** and **Critical threshold**: Thresholds that when reached by the returned value change the status of the module to **warning** status or **critical** status. You may use the **Inverse interval** option to define that the warning/critical status //is any value outside this range//.
* **Change to critical status after **X** intervals in warning status**: From PFMS version 766 onwards there is the possibility to //promote// the change to critical status of a module __if it has been in warning status N times in a row__ (continuous monitoring intervals) __in warning status__. The main difference with **FF threshold** is that such functionality delays the status change while **Change to critical status after** favors it. Always keep in mind that both options work in conjunction with each other.
* **Change to critical status after **X** intervals in warning status**: From PFMS version 766 onwards there is the possibility to //promote// the change to critical status of a module __if it has been in warning status N times in a row__ (continuous monitoring intervals) __in warning status__. The main difference with **FF threshold** is that such functionality delays the status change while **Change to critical status after** favors it. Always keep in mind that both options work in conjunction with each other.
* **警告状態 X 回後に障害状態に変更(Change to critical status after **X** intervals in warning status)**: Pandora FMS バージョン 766 以降では、__モジュールが連続して N 回警告状態が続いた場合(継続的な監視間隔)__に、モジュールを障害状態へ変更することができます。**連続抑制回数** との主な違いは、それがステータスの変更を遅らせるのに対し、**障害状態への変更** を優先することです。 両方のオプションが相互に連携して機能することを常に念頭に置いてください。
* **警告状態 X 回後に障害状態に変更(Change to critical status after **X** intervals in warning status)**: Pandora FMS バージョン 766 以降では、__モジュールが連続して N 回警告状態が続いた場合(継続的な監視間隔)__に、モジュールを障害状態へ変更することができます。**連続抑制回数** との主な違いは、それがステータスの変更を遅らせるのに対し、**障害状態への変更** を優先することです。 両方のオプションが相互に連携して機能することを常に念頭に置いてください。
行 382:
行 415:
=== 高度なオプション ===
=== 高度なオプション ===
-
<WRAP center round important 60%>Always keep in mind that this interface is used by [[:en:documentation:03_monitoring:01_intro_monitoring#monitoring_by_software_agent_vs._remote_monitoring|both local monitoring and remote monitoring]] and presents parameters that are valid in one or the other domain. For example, the **Timeout** and **Retries** parameters are not useful in local monitoring (local checks) but are important in remote monitoring.
+
<WRAP center round important 90%>
-
</WRAP>\\
+
You should always bear in mind that this interface is used by both [[#ks2|local monitoring as well as by remote monitoring]] and valid parameters are presented in one field or another. For example, the parameters **Timeout** and **Retries** (Retries) are useless in local monitoring (local checks) but are important in remote monitoring.
-
<WRAP center round important 60%>このインターフェースは[[:ja:documentation:03_monitoring:01_intro_monitoring#ソフトウエアエージェントでのモニタリングと_リモートモニタリング|ローカルモニタリングとリモートモニタリングの両方]]によって使用され、いずれかの範囲で有効なパラメーターを設定することを常に念頭に置いてください。 たとえば、**タイムアウト(Timeout)** および **リトライ(Retries)** パラメーターは、ローカル監視(ローカルチェック)では役立ちませんが、リモート監視では重要です。
* **Custom ID**: Field to store a custom identification value.
* **Custom ID**: Field to store a custom identification value.
* **Unit**: For choice unit of the data received by the module, by default empty. You may either choose a specific unit (Timeticks, Bytes, Entries, etc.) or click on the pencil icon [[https://prewebs.pandorafms.com/manual/_detail/wiki/icon_pencil.png?id=es:documentation:03_monitoring:01_intro_monitoring|{{https://prewebs.pandorafms.com/manual/_media/wiki/icon_pencil.png?nolink&}}]] to set custom units.
* **Unit**: For choice unit of the data received by the module, by default empty. You may either choose a specific unit (Timeticks, Bytes, Entries, etc.) or click on the pencil icon [[https://prewebs.pandorafms.com/manual/_detail/wiki/icon_pencil.png?id=es:documentation:03_monitoring:01_intro_monitoring|{{https://prewebs.pandorafms.com/manual/_media/wiki/icon_pencil.png?nolink&}}]] to set custom units.
* **Interval:** Period in which the module should return data. If a module does not receive data during more than two intervals, it will go into in unknown state.
* **Interval:** Period in which the module should return data. If a module does not receive data during more than two intervals, it will go into in unknown state.
-
* If they are remote modules: Time period during which the remote check takes place.
+
- If they are remote modules: period in which the remote check is carried out.
-
* If they are data modules: Remote module that represents N times the interval of the defined agent, doing the local check during that time.
+
- If they are data modules: numerical value that represents X times the interval of the defined agent, performing the local check in that period.
+
- In the case of Broker Agents via Web Console, from version 776 onwards, their interval is not displayed to prevent unwanted changes.
* **Post process:** It allows to specify carrying out a post-processing, a module-received data conversion. Disabled by default (0). Available modules:
* **Post process:** It allows to specify carrying out a post-processing, a module-received data conversion. Disabled by default (0). Available modules:
* Seconds to months.
* Seconds to months.
行 412:
行 449:
* **Discard unknown events**: It allows to discard unknown events.
* **Discard unknown events**: It allows to discard unknown events.
* **FF threshold:** It allows setting thresholds for [[:en:documentation:01_understanding:03_glossary#flip-flop_protection|FlipFlop protection]]. FlipFlop (FF) is known as a common phenomenon in monitoring: when a value fluctuates frequently between alternative values (RIGHT/WRONG). When this takes place, a "threshold" is usually used, so that in order to consider something as having changed status, it has to "stay" more than N intervals in a state without changing. //FF threshold// is used to 'filter' the continuous status changes in the creation of events/statuses: that way Pandora FMS knows that, until an element has adopted the same status at least N times in the same status after having changed from an original status, it will not be considered as changed.
* **FF threshold:** It allows setting thresholds for [[:en:documentation:01_understanding:03_glossary#flip-flop_protection|FlipFlop protection]]. FlipFlop (FF) is known as a common phenomenon in monitoring: when a value fluctuates frequently between alternative values (RIGHT/WRONG). When this takes place, a "threshold" is usually used, so that in order to consider something as having changed status, it has to "stay" more than N intervals in a state without changing. //FF threshold// is used to 'filter' the continuous status changes in the creation of events/statuses: that way Pandora FMS knows that, until an element has adopted the same status at least N times in the same status after having changed from an original status, it will not be considered as changed.
-
* **FF interval:** If the flip-flop threshold is activated and there is a state change, the module interval will change for the next execution.
+
* **FF Interval**: Allows to specify a shorter time interval for the next check if a Flip Flop threshold is activated in the module. When FF is enabled and a change of state is detected that meets the set check conditions, **the module interval for the next run will be adjusted**. This setting facilitates faster checks when specific conditions are needed by setting a value smaller than the main module interval.
* **FlipFlop timeout:** Parameter that can only be used in asynchronous modules. For a state change by flip-flop to be effective, equal consecutive data must be received within the specified interval.
* **FlipFlop timeout:** Parameter that can only be used in asynchronous modules. For a state change by flip-flop to be effective, equal consecutive data must be received within the specified interval.
* **Tags available** and **Tags from policy**: These are features of the Enterprise version. They are detailed in the following [[:en:documentation:03_monitoring:01_intro_monitoring#tags|section "Tags"]].
* **Tags available** and **Tags from policy**: These are features of the Enterprise version. They are detailed in the following [[:en:documentation:03_monitoring:01_intro_monitoring#tags|section "Tags"]].
行 422:
行 459:
* **Interval:** Period in which the module should return data. If a module does not receive data during more than two intervals, it will go into in unknown state.
* **Interval:** Period in which the module should return data. If a module does not receive data during more than two intervals, it will go into in unknown state.
Where “n” can be an unsigned (positive) or negative number and FORMAT follows the standard of [[http://search.cpan.org/~dexter/POSIX-strftime-GNU-0.02/lib/POSIX/strftime/ GNU.pm|perl strftime]].
* **Module relations**: Used to replace the module, either directly (**Direct**) or on failover (**Failover**), for the purposes of [[:en:documentation:pandorafms:management_and_operation:08_data_presentation_reports#availability_graph|SLA calculation]].
+
* **Ignore unknown**: This disables the calculation of the unknown state in the module, so the transition to unknown will never be performed. The state it reflects is the last known state.
They can also be used to grant specific access permissions to a module, so that [[:en:documentation:04_using:11_managing_and_administration#extended_permission_systems_through_tags|a user can access]] only one module of the agent, without having access to the rest of modules.
+
They can also be used to grant specific access permissions to a module, so that [[:en:documentation:pandorafms:management_and_operation:11_managing_and_administration#extended_permission_systems_through_tags|a user can access]] only one module of the agent, without having access to the rest of modules.
You may also run actions such as editing the module by clicking on its name. The actions column (<wrap :en>**Actions**</wrap>) contains, from left to right:
* Duplicate a module (the following prefix will be added <wrap :en>**copy of…**</wrap>)
+
* Normalize values: This will delete the extreme values above and below most of the values, this action is irreversible and confirmation will be performed before deleting these extreme values.
* **Dynamic Threshold Max.**: Maximum value of the critical dynamic threshold, if a tolerance margin is set (in percentage) for it; For instance, if the average values are around 60 and the critical threshold has been set from value 80, if the value Dynamic Threshold Max: 10 is set, this critical threshold will increase by 10%, so it would remain at a value of 88.
* **Dynamic Threshold Max.**: Maximum value of the critical dynamic threshold, if a tolerance margin is set (in percentage) for it; For instance, if the average values are around 60 and the critical threshold has been set from value 80, if the value Dynamic Threshold Max: 10 is set, this critical threshold will increase by 10%, so it would remain at a value of 88.
* **Dynamic Threshold Min.**:It allows you to reduce the lower limit by the percentage indicated. For example, if the average values are around 60 and the lower critical threshold has been set to a value of 40, if the value Dynamic Threshold Min: 10 is set, this critical threshold will be reduced by 10%, so it would take a value of 36.
* **Dynamic Threshold Min.**:It allows you to reduce the lower limit by the percentage indicated. For example, if the average values are around 60 and the lower critical threshold has been set to a value of 40, if the value Dynamic Threshold Min: 10 is set, this critical threshold will be reduced by 10%, so it would take a value of 36.
-
* **Dynamic Threshold Two Tailed**: These are dynamic threshold intervals, which are disabled by default. If this option is activated, the dynamic threshold system will **also** set thresholds **below** the average.
+
* **Dynamic Threshold Two Tailed**: Only for dynamic thresholds. This option allows to increase both the minimum and maximum module threshold ranges according to the average provided by the dynamic threshold. This option includes both positive and negative values.
Access **Management** → **Module library** → **View** to access the main view. You can also group by categories (databases, virtualization, etc.) or search for the plugin by its name in the **Search** text box.
+
Access **Management → Module library → View** to access the main view. You can also group by categories (databases, virtualization, etc.) or search for the plugin by its name in the **Search** text box.
* The **username and password** [[:en:documentation:04_using:12_console_setup#module_library|that has been configured]] in the setup must match the one of **Integria IMS** support.
+
* The **username and password** [[:en:documentation:pandorafms:management_and_operation:12_console_setup#module_library|that has been configured]] in the setup must match the one of **Pandora ITSM** support.
-
* The **version** of Pandora FMS is **Enterprise**.