Jump to content


Email Notification

  • Please log in to reply
3 replies to this topic

#1 zulf



  • Members
  • PipPip
  • 19 posts

Posted 28 July 2008 - 01:41 PM

I have enabled mail notification and does get email notifications with some of the events. Last week our replication failed and monyog never emailed on this. (which performance metrics should be configured for Mail Alert if we need to get notified when replication is stopped/started/failed?

Also we had to shutdown and restart MySQL instance for some configuration changes, and never got any email notification from Monyog saying MySQL was shutdown. Again something that need to be configured here also?

Please advice.

#2 Mahesh


    Advanced Member

  • Members
  • PipPipPip
  • 499 posts
  • Gender:Male
  • Location:Bangalore,India

Posted 29 July 2008 - 05:18 AM

by default Mail Alert is enabled for
Replication -- Slave running(replication 01), Slave I/O running(replication 02),Slave SQL Running(replication -04) and Seconds behind master(replication -05). and also for General Info -- Available (general info 01)Counters.
If the mail alert is not enabled for this counter then you can enabled it by setting "MailAlert : "Yes" by editing particular .js( as mentioned above) file in Tools-- Customize section.

If you have already enabled an Alert for this counter then at that instance in Notification Settings -- Send mails is (yes/no) and minimum notification interval, it depends on this too.


#3 cloudcontrol



  • Members
  • Pip
  • 4 posts

Posted 23 April 2012 - 08:16 PM

While we have received alerts when we replication is X seconds behind the master, the error state we encountered Sunday (see attached history export) did not trigger an alert. We find it hard to believe our error condition is not by default one that would generate and email notification.

The circumstances where that the replicas were reporting the following error: Got fatal error 1236 from master when reading data from binary log: 'Client requested master to start replication from impossible position'

We know that this was caused by a RDS master failover on AWS, abd as you can see from the moyog report, replication was completely broken. How can we make sure MONyog alerts us if this happens in the future?


#4 haimari



  • Members
  • Pip
  • 1 posts

Posted 12 February 2013 - 01:41 PM

would like to know that too

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users