Details
-
Help
-
Resolution: Not A Bug
-
Trivial
-
None
-
Professional Edition
-
Observium 20.11.10844 (26th November 2020)
OS Linux 4.9.0-4-amd64 [amd64] (Debian 9.2)
Apache 2.4.25 (Debian)
PHP 7.0.19-1 (OPcache: ENABLED) (Memory: 1GB)
Python 2.7.13
MariaDB 10.1.26-MariaDB-0+deb9u1 (extension: mysqli 5.0.12-dev)
SNMP NET-SNMP 5.7.3
RRDtool 1.6.0 (rrdcached 1.6.0: unix:/var/run/rrdcached.sock)
Fping 3.15 (IPv4 and IPv6)Observium 20.11.10844 (26th November 2020) OS Linux 4.9.0-4-amd64 [amd64] (Debian 9.2) Apache 2.4.25 (Debian) PHP 7.0.19-1 (OPcache: ENABLED) (Memory: 1GB) Python 2.7.13 MariaDB 10.1.26-MariaDB-0+deb9u1 (extension: mysqli 5.0.12-dev) SNMP NET-SNMP 5.7.3 RRDtool 1.6.0 (rrdcached 1.6.0: unix:/var/run/rrdcached.sock) Fping 3.15 (IPv4 and IPv6)
Description
Hello,
We created a new port alert to detect errors in the port, when they are greater or equal to 1, for 3 condition as this:
ifErrors_rate ge 1
ifInErrors_rate ge 1
ifOutErrors_rate ge 1
The first thing, in the metric ifOutErrors_rate doesn't appear in the status, and the checks said is OK when the values measured is greater or equal to the condition, as this:
We did try another values for the condition like 1.0, 2, 2.0, but with the same outcome:
What to do so the 3 conditions are been tested, and what is the correct format for the value condition?
Thanks.
Attachments
Activity
Indeed it was that, we did not set "Require ANY condition".
Derp mistake.
Thanks and happy holidays!!!
Probably you was not set "Require ANY condition":
I tested same conditions with Require ANY condition option, alert triggered as expected.
Second question about **ifOutErrors_rate - it has a zero value, so it does not appear in this case.**
When there is also a non-zero value, it will be displayed too.
I'd recommend only using ifErrors_rate in the check, since it's synthesised by us as in+out, using in and out should only be done when you want to test one of them independently. Just using ifErrors_rate will reduce the data storage load on the database for this test.