Ad Widget

Collapse

False Alarms from Triggers

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • tmroberts
    Member
    Zabbix Certified SpecialistZabbix Certified Professional
    • Jan 2017
    • 73

    #1

    False Alarms from Triggers

    I'm in the process of trying to set up monitoring of a handful of MongoDB instances using this method: link. MongoDB (version 3.4 is on Ubuntu 14.04.3) and Zabbix Server (version 3.2) is running on CentOS (version 7 i believe) I have two different instances running on MongoDB. Both are version 3.4 but one is running with SSL.

    PROBLEM: All of the metrics I'm interested in monitoring work. Specifically, number of active connections and number of available connections. The issue is the Triggers that I have created. I want to know when the instance has reached 75% and subsequently 90% of available connections. I've done this a million times on other platforms and it works perfectly. On Mongo however, even with correct numbers being returned the triggers are going off.... Here's an example:

    mongodb34 has 15 active connections and is reporting back with 51185 available connections. Yet the trigger has been tripped telling me that I have exceeded both 75 and 90% thresholds.

    I have verified that the datatype for each key is a numeric value, latest data is reporting back correctly. Here's an example of the expression I'm using for the 75% threshold from the template:

    {Databases - DBZ MongoDB:mongodb.connections.current.last(,0)}>=({D atabases - DBZ MongoDB:mongodb.connections.current.last(,0)}*.75)

    Am I doing something wrong? If so what? I have been staring at this for two days and not come up with anything.
Working...