2009-10-20 Sancho Lerena <slerena@artica.es>

RC1 Release

        * include/help/en/help_ff_threshold.php: Added missing help topic.

        * general/error_perms.php, general/error_install.php: Removed print of 
        version, don't know this variable at this point.



git-svn-id: https://svn.code.sf.net/p/pandora/code/trunk@2042 c3f86ba8-e40f-0410-aaad-9ba5e7f4b01f
This commit is contained in:
slerena 2009-10-20 21:32:38 +00:00
parent cf8e8ca556
commit 5de26c4bc5
5 changed files with 52 additions and 3 deletions

View File

@ -1,3 +1,12 @@
2009-10-20 Sancho Lerena <slerena@artica.es>
RC1 Release
* include/help/en/help_ff_threshold.php: Added missing help topic.
* general/error_perms.php, general/error_install.php: Removed print of
version, don't know this variable at this point.
2009-10-20 Miguel de Dios <miguel.dedios@artica.es>
* pandora_console/operation/menu.php,

View File

@ -38,7 +38,6 @@
<h1 id="log_f" class="error">Installer active</h1>
<div>
<img src="images/pandora_logo.png" border="0"></a><br><font size="1">
<?php echo $pandora_version; ?>
</font>
</div>
<div class="msg"><br><br>

View File

@ -36,7 +36,6 @@
<h1 id="log_f" class="error">Bad permission for include/config.php</h1>
<div>
<img src="images/pandora_logo.png" border="0"></a><br>
<font size="1"><?php echo $pandora_version; ?></font>
</div>
<div class="msg"><br><br>
For security reasons, <i>config.php</i> must have restrictive permissions, and "other" users

View File

@ -22,7 +22,7 @@
/**
* Pandora build version and version
*/
$build_version = 'PC091016';
$build_version = 'PC091020';
$pandora_version = 'v3.0RC1';
$config['start_time'] = microtime (true);

View File

@ -0,0 +1,42 @@
<?php
/**
* @package Include/help/en
*/
?>
<h1>Module Flip Flop Threshold</h1>
<br>
<br>
The Threshold parameter FF (FF = FlipFlop) is used to "filter" the continuous changes of state in the generation of events / states, so that you can tell Pandora FMS until an element is not at least X times in the same state after changing from an original state, not considered to have changed.
<br><br>
Take a classic example: A ping to a host where there is packet loss. In an environment like this, might give results as:
<br>
<pre>
1
1
0
1
1
0
1
1
1
</pre>
<br>
However, the host is alive in all cases. What we really want is to tell Pandora that until the host does not say you are at least three times down, not marked as such, so that in the previous case and would never be dropped, and only in this case it would be:
<pre>
1
1
0
1
0
0
0
</pre>
<br>
From this point you would see as down, but not before.
<br>
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) .