![](https://secure.gravatar.com/avatar/0fa97865a0e1ab36152b6b2299eedb49.jpg?s=120&d=mm&r=g)
It's odd, since we've added code to prevent this kind of thing happening, but devices still manage to send us data which make it happen. Ho hum!
adam. On 16/12/2015 14:21:00, Spencer Ryan sryan@arbor.net wrote: Almost 100% it's the Juniper.
You could add another check for that alert where both conditions must be true and add ifInOctetc_perc le 100
Spencer Ryan | Senior Systems Administrator | sryan@arbor.net [mailto:sryan@arbor.net] Arbor Networks +1.734.794.5033 (d) | +1.734.846.2053 (m) www.arbornetworks.com [http://www.arbornetworks.com/]
On Wed, Dec 16, 2015 at 3:06 AM, Anders Johansson <Anders.Johansson@direktorn.com [mailto:Anders.Johansson@direktorn.com]> wrote:
Hi All,
I've started to setup alarms in Observium, works really great. However a few alarms is bugging me:
This device seems to have a utilitzation rate at about 2222% ? I've seen a few of these and not sure why. I can view the percentage usage on the port in observium (durin the time windows the alarm firerd)
Is this an error occuring at the Juniper side, or somewhere else in the chain?
//Anders
_______________________________________________ observium mailing list observium@observium.org [mailto:observium@observium.org] http://postman.memetic.org/cgi-bin/mailman/listinfo/observium [http://postman.memetic.org/cgi-bin/mailman/listinfo/observium]
_______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium