2014-06-24 Ramon Novoa <rnovoa@artica.es>
* godmode/agentes/module_manager_editor_common.php, include/help/en/help_ff_interval.php, include/help/en/help_ff_threshold.php, include/help/en/help_ff_timeout.php, include/help/es/help_ff_interval.php, include/help/es/help_ff_threshold.php, include/help/es/help_ff_timeout.php, include/help/ja/help_ff_interval.php, include/help/ja/help_ff_threshold.php, include/help/ja/help_ff_timeout.php: Updated help files for the FF threshold. git-svn-id: https://svn.code.sf.net/p/pandora/code/trunk@10270 c3f86ba8-e40f-0410-aaad-9ba5e7f4b01f
This commit is contained in:
Ramon Novoa
parent
34d4abede6
commit
5cb5106b1d
|
|
@ -1,3 +1,16 @@
|
|||
2014-06-24 Ramon Novoa <rnovoa@artica.es>
|
||||
|
||||
* godmode/agentes/module_manager_editor_common.php,
|
||||
include/help/en/help_ff_interval.php,
|
||||
include/help/en/help_ff_threshold.php,
|
||||
include/help/en/help_ff_timeout.php,
|
||||
include/help/es/help_ff_interval.php,
|
||||
include/help/es/help_ff_threshold.php,
|
||||
include/help/es/help_ff_timeout.php,
|
||||
include/help/ja/help_ff_interval.php,
|
||||
include/help/ja/help_ff_threshold.php,
|
||||
include/help/ja/help_ff_timeout.php: Updated help files for the FF threshold.
|
||||
|
||||
2014-06-24 Junichi Satoh <junichi@rworks.jp>
|
||||
|
||||
* include/functions_api.php: Added support for 'each_ff' and
|
||||
|
|
|
|||
|
|
@ -388,12 +388,13 @@ $table_advanced->data[4][3] = __('Throw unknown events');
|
|||
$table_advanced->data[4][4] = html_print_checkbox('throw_unknown_events',
|
||||
1, $throw_unknown_events_check, true);
|
||||
|
||||
$table_advanced->data[5][0] = __('FF interval');
|
||||
$table_advanced->data[5][0] = __('FF interval') . ' ' . ui_print_help_icon ('ff_interval', true);
|
||||
$table_advanced->data[5][1] = html_print_input_text ('module_ff_interval', $ff_interval,
|
||||
'', 5, 10, true, $disabledBecauseInPolicy).ui_print_help_tip (__('Module execution flip flop time interval (in secs).'), true);
|
||||
$table_advanced->colspan[5][1] = 2;
|
||||
|
||||
$table_advanced->data[5][3] = __('FF timeout');
|
||||
$table_advanced->data[5][3] = __('FF timeout') . ' ' . ui_print_help_icon ('ff_timeout', true);
|
||||
|
||||
$module_type_name = modules_get_type_name($id_module_type);
|
||||
if (preg_match ('/async/', $module_type_name) || $edit) {
|
||||
$table_advanced->data[5][4] = '<span id="ff_timeout">' . html_print_input_text ('ff_timeout', $ff_timeout,
|
||||
|
|
|
|||
|
|
@ -0,0 +1,57 @@
|
|||
<?php
|
||||
/**
|
||||
* @package Include/help/en
|
||||
*/
|
||||
?>
|
||||
<h1>Module Flip Flop Interval</h1>
|
||||
|
||||
<br><br>
|
||||
|
||||
If FF threshold is greater than 0, several consecutive values are required to change the status of a module. But if you want subsequent cheks to be performed at a different interval you can specify it with FF interval.
|
||||
|
||||
For example, a ping module with a 5 minute interval, a FF threshold of 1 and a FF interval of 60 seconds would behave in the following way:
|
||||
|
||||
<br><br>
|
||||
<table>
|
||||
<th>Time</th>
|
||||
<th>Data</th>
|
||||
<th>Status change</th>
|
||||
<tr>
|
||||
<td>12:00</td>
|
||||
<td>1</td>
|
||||
<td>No</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>12:05</td>
|
||||
<td>1</td>
|
||||
<td>No</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>12:10</td>
|
||||
<td>0</td>
|
||||
<td>No</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><b>12:11</b></td>
|
||||
<td>1</td>
|
||||
<td>No</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>12:16</td>
|
||||
<td>1</td>
|
||||
<td>No</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>12:21</td>
|
||||
<td>0</td>
|
||||
<td>No</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><b>12:22</b></td>
|
||||
<td>0</td>
|
||||
<td><b>Yes</b></td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
<br><br>
|
||||
|
||||
|
|
@ -40,5 +40,4 @@ From this point you would see as down, but not before.
|
|||
Protection anti Flip-Flop is used to avoid those annoying fluctuations, all modules implement it and use it to avoid the change of state (defined by their defined limits or boundaries machines, as is the case with modules * proc) .
|
||||
|
||||
<br><br>
|
||||
<b>NOTICE</b>: Due Keepalive only notify ONCE per change. This parameter SHOULD NOT be used in KeepAlive modules.
|
||||
|
||||
|
|
|
|||
|
|
@ -0,0 +1,52 @@
|
|||
<?php
|
||||
/**
|
||||
* @package Include/help/en
|
||||
*/
|
||||
?>
|
||||
<h1>Module Flip Flop Timeout</h1>
|
||||
|
||||
<br><br>
|
||||
|
||||
If FF threshold is greater than 0, several consecutive values are required to change the status of a module. This works well for synchronous modules, but since asynchronous modules do not send data at regular intervals, checking for consecutive values may not be that useful if they are far away in time. Thus, if FF timeout is greater than 0, consecutive values must occur within the configured time interval.
|
||||
|
||||
For example, an asynchronous proc module with a FF threshold of 1 and a FF timeout of 600 (10 minutes) would behave in the following way:
|
||||
|
||||
<br><br>
|
||||
<table>
|
||||
<th>Time</th>
|
||||
<th>Data</th>
|
||||
<th>Status change</th>
|
||||
<tr>
|
||||
<td>12:00</td>
|
||||
<td>1</td>
|
||||
<td>No</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>12:05</td>
|
||||
<td>0</td>
|
||||
<td>No</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><b>12:20</b></td>
|
||||
<td>0</td>
|
||||
<td>No</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>12:25</b></td>
|
||||
<td>1</td>
|
||||
<td>No</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>12:45</td>
|
||||
<td>0</td>
|
||||
<td>No</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><b>12:50</b></td>
|
||||
<td>0</td>
|
||||
<td><b>Yes</b></td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
<br><br>
|
||||
|
||||
|
|
@ -0,0 +1,57 @@
|
|||
<?php
|
||||
/**
|
||||
* @package Include/help/es
|
||||
*/
|
||||
?>
|
||||
<h1>Intervalo de Flip Flop del Módulo</h1>
|
||||
|
||||
<br><br>
|
||||
|
||||
Si el umbral de FF es mayor que 0, se necesitan varios valores consecutivos para cambiar el estado del módulo. Pero si desea que las subsiguientes comprobaciones se ejecuten con un intervalo diferente lo puede especificar mediante el intervalo de FF.
|
||||
|
||||
Por ejemplo, un módulo de ping con un intervalo de 5 minutos, un umbral de FF de 1 y un intervalo de FF de 60 segundos se comportaría de la siguiente forma:
|
||||
|
||||
<br><br>
|
||||
<table>
|
||||
<th>Time</th>
|
||||
<th>Data</th>
|
||||
<th>Status change</th>
|
||||
<tr>
|
||||
<td>12:00</td>
|
||||
<td>1</td>
|
||||
<td>No</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>12:05</td>
|
||||
<td>1</td>
|
||||
<td>No</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>12:10</td>
|
||||
<td>0</td>
|
||||
<td>No</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><b>12:11</b></td>
|
||||
<td>1</td>
|
||||
<td>No</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>12:16</td>
|
||||
<td>1</td>
|
||||
<td>No</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>12:21</td>
|
||||
<td>0</td>
|
||||
<td>No</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><b>12:22</b></td>
|
||||
<td>0</td>
|
||||
<td><b>Yes</b></td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
<br><br>
|
||||
|
||||
|
|
@ -46,6 +46,4 @@ Desde este punto lo vería como caído, pero no antes.
|
|||
La protección anti FLip-flop se usa para evitar estas fluctuaciones tan molestas, todos los módulos la implementan y la utilizan para evitar el cambio de estado (definido por sus limites definidos o sus sistemas diferenciales, como por ejemplo ocurre con los módulos *proc).
|
||||
|
||||
<br><br>
|
||||
<b>AVISO</b>: Dado que los modulos KeepAlive solo cambian de estado una vez, este parámetro no se debería usar nunca con modulos Keepalive.
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -0,0 +1,52 @@
|
|||
<?php
|
||||
/**
|
||||
* @package Include/help/es
|
||||
*/
|
||||
?>
|
||||
<h1>Timeout de Flip Flop del módulo</h1>
|
||||
|
||||
<br><br>
|
||||
|
||||
Si el umbral de FF es mayor que 0, se necesitan varios valores consecutivos para cambiar el estado del módulo. Pero si desea que las subsiguientes comprobaciones se ejecuten con un intervalo diferente lo puede especificar mediante el intervalo FF. Esto funciona bien para módulos síncronos, pero como los módulos asíncronos no envían datos en intervalos regulares, comprobar valores consecutivos puede no resultar muy útil si están muy separados en el tiempo. Así, si el timeout de FF del módulo es mayor que 0, los valores consecutivos deben ocurrir dentro del intervalo de tiempo especificado.
|
||||
|
||||
Por ejemplo, un módulo asíncrono de tipo proc con un umbral de FF de 1 y un timeout de FF de 600 (10 minutos) se comportaría de la siguiente forma:
|
||||
|
||||
<br><br>
|
||||
<table>
|
||||
<th>Time</th>
|
||||
<th>Data</th>
|
||||
<th>Status change</th>
|
||||
<tr>
|
||||
<td>12:00</td>
|
||||
<td>1</td>
|
||||
<td>No</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>12:05</td>
|
||||
<td>0</td>
|
||||
<td>No</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><b>12:20</b></td>
|
||||
<td>0</td>
|
||||
<td>No</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>12:25</b></td>
|
||||
<td>1</td>
|
||||
<td>No</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>12:45</td>
|
||||
<td>0</td>
|
||||
<td>No</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><b>12:50</b></td>
|
||||
<td>0</td>
|
||||
<td><b>Yes</b></td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
<br><br>
|
||||
|
||||
|
|
@ -0,0 +1,57 @@
|
|||
<?php
|
||||
/**
|
||||
* @package Include/help/ja
|
||||
*/
|
||||
?>
|
||||
<h1>Module Flip Flop Interval</h1>
|
||||
|
||||
<br><br>
|
||||
|
||||
If FF threshold is greater than 0, several consecutive values are required to change the status of a module. But if you want subsequent cheks to be performed at a different interval you can specify it with FF interval.
|
||||
|
||||
For example, a ping module with a 5 minute interval, a FF threshold of 1 and a FF interval of 60 seconds would behave in the following way:
|
||||
|
||||
<br><br>
|
||||
<table>
|
||||
<th>Time</th>
|
||||
<th>Data</th>
|
||||
<th>Status change</th>
|
||||
<tr>
|
||||
<td>12:00</td>
|
||||
<td>1</td>
|
||||
<td>No</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>12:05</td>
|
||||
<td>1</td>
|
||||
<td>No</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>12:10</td>
|
||||
<td>0</td>
|
||||
<td>No</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><b>12:11</b></td>
|
||||
<td>1</td>
|
||||
<td>No</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>12:16</td>
|
||||
<td>1</td>
|
||||
<td>No</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>12:21</td>
|
||||
<td>0</td>
|
||||
<td>No</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><b>12:22</b></td>
|
||||
<td>0</td>
|
||||
<td><b>Yes</b></td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
<br><br>
|
||||
|
||||
|
|
@ -45,4 +45,3 @@
|
|||
この機能は、すべてのモジュールにおいて実装されています。
|
||||
|
||||
<br><br>
|
||||
<b>注意</b>: Keepalive は 1回の変化のみ通知するため、KeepAlive モジュールではこのパラメータは使わないでください。
|
||||
|
|
|
|||
|
|
@ -0,0 +1,52 @@
|
|||
<?php
|
||||
/**
|
||||
* @package Include/help/ja
|
||||
*/
|
||||
?>
|
||||
<h1>Module Flip Flop Timeout</h1>
|
||||
|
||||
<br><br>
|
||||
|
||||
If FF threshold is greater than 0, several consecutive values are required to change the status of a module. This works well for synchronous modules, but since asynchronous modules do not send data at regular intervals, checking for consecutive values may not be that useful if they are far away in time. Thus, if FF timeout is greater than 0, consecutive values must occur within the configured time interval.
|
||||
|
||||
For example, an asynchronous proc module with a FF threshold of 1 and a FF timeout of 600 (10 minutes) would behave in the following way:
|
||||
|
||||
<br><br>
|
||||
<table>
|
||||
<th>Time</th>
|
||||
<th>Data</th>
|
||||
<th>Status change</th>
|
||||
<tr>
|
||||
<td>12:00</td>
|
||||
<td>1</td>
|
||||
<td>No</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>12:05</td>
|
||||
<td>0</td>
|
||||
<td>No</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><b>12:20</b></td>
|
||||
<td>0</td>
|
||||
<td>No</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>12:25</b></td>
|
||||
<td>1</td>
|
||||
<td>No</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>12:45</td>
|
||||
<td>0</td>
|
||||
<td>No</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><b>12:50</b></td>
|
||||
<td>0</td>
|
||||
<td><b>Yes</b></td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
<br><br>
|
||||
|
||||
Loading…
Reference in New Issue