[slibby]

Hello Siddhant,

 

We are still not showing any relevant entries in MONyog.log around the time frames when these alerts should have been sent.  Also, the “alert-able” configuration has been set to 1 instead of the default value of 5 for all servers since prior to our realization that the alerts were not being sent occasionally.

 

I am sending an email with the Dropbox links to the events.data files for two of our servers which have been configured to alert on our ‘Notification Test’ monitor.  The CSO was originally applied to one server, then we switched it to apply to a different server early this morning.

 

Thank you,

Steven Libby

[slibby]

Thanks for the explanation Mahesh.

 

My confusion came about because I thought the monitor alerted based on the Current value (which uses the values of the global status variables from the MySQL server).  However, since you mentioned that this monitor is based on Delta values, I noticed that this only takes into account the differences between the last two collections, which is why the monitor was alerting us.  In our environment, there may be times when only 2 connection attempts occur within a minute, and if both of those are Aborted_connects, then the Delta value returns 100%.

 

Is there a list of monitors which are based on Delta values, as opposed to Current values?  For instance, “MySQL Logs: Recent entries of type [ERROR]” is based on current values, while “Connection History: Percentage of refused connections” is based on delta values.  Or perhaps is there a way to determine this based on the monitor group?

 

Thanks again.

[Author]

Posts