<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 75%>You should always bear in mind that this interface is used by both [[#comparacion_de_la_monitorizacion_basada_en_agentes_software_y_en_monitorizacion_remota|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>\\
+
</WRAP>
-
<WRAP center round important 60%>このインターフェースは[[:ja:documentation:03_monitoring:01_intro_monitoring#ソフトウエアエージェントでのモニタリングと_リモートモニタリング|ローカルモニタリングとリモートモニタリングの両方]]によって使用され、いずれかの範囲で有効なパラメーターを設定することを常に念頭に置いてください。 たとえば、**タイムアウト(Timeout)** および **リトライ(Retries)** パラメーターは、ローカル監視(ローカルチェック)では役立ちませんが、リモート監視では重要です。
+
<WRAP center round important 75%>このインターフェースは[[#ソフトウエアエージェントでのモニタリングと_リモートモニタリング|ローカルモニタリングとリモートモニタリングの両方]]によって使用され、いずれかの範囲で有効なパラメーターを設定することを常に念頭に置いてください。 たとえば、**タイムアウト(Timeout)** および **リトライ(Retries)** パラメーターは、ローカル監視(ローカルチェック)では役立ちませんが、リモート監視では重要です。
-
</WRAP>\\
+
</WRAP>
{{ :wiki:parametros_comunes_modulos2.png }}
{{ :wiki:parametros_comunes_modulos2.png }}
行 394:
行 396:
* **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:
行 415:
* **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:
行 425:
* **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.
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**.