-
How is FF Threshold working? Possibly not at all in my case…
Hi!
I have got a question about the FF Threshold one can define for monitors. From the provided description I thought that a monitor can go into critical values x-1 times in a row without becoming critical itself if the FF Threshold is being set to x. Is that the right interpretation?
I have a montior from a software agent which returns a generic_data value. A value of 0 is just fine (0 problems). A value of >0 is a problem. Therefore I configured the agent so that Warning Min:0 Max:0 and Critical Min:1 Max:0.
However, the value can become >0 for a short time during maintenance which is no problem so I’ve set the FF Threshold to 3. The agent sents new data every 240 seconds. I also configured an alert for the monitor which sends a XMPP message from 1 to 10 alerts.
The problem is, it does not work as expected. Whenever the value becomes >0 and the agent sends new data to the server, the monitor instantly goes critical and I get a XMPP message telling me about it.
What am I doing wrong? What am I not getting here?
Thanks in advance for help!
Florian
-
3 Replies
-
-
Are you using the latest 3.0 version ?.
My problem is (see the other post at http://openideas.info/smf/index.php?topic=1272.0), what does latest 3.0 version mean? I have the 3.0 version as .deb package from sourceforge running on Ubuntu 10.04 Server. However, the console tells me there is an update available which I cannot install.
Nevertheless, I’m using Pandora FMS 3.0. So the answer is yes.
Do you come from a upgrade or just the 3.0 version ?
It’s a fresh install on a fresh Ubuntu 10.04 Server machine from .deb package.
-
Hi Florian,
It works the way you described starting from 3.1. In 3.0 it checked events, not module status. The full feature was not yet implemented, even though the documentation said so. You can get the latest code from the project’s subversion repository or wait for 3.1 RC1, which will be out in about a week.
