If you plan on constructing this your self may I suggest that you create a matrix of all the possible scenarios/issues you would like to trap and define how you want to those `automatically` handled. For example, `replication stopped`, `duplicate index`, `long running query`, `corrupt table`, etc, and what action to take and who should be notified. A cron job that runs every fifteen or thirty or whatever the desired interval could start the monitoring process and each run could be logged. ... This is only a suggestion of course.
>>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<< On 3/3/04, 9:24:20 AM, Peter <[EMAIL PROTECTED]> wrote regarding Mysql monitor: > Hi, > Due to poor database design and heavy load, database tables get corrupted a > lot. > I want to monitor that process and once a table to get corrupted to repair > it on the fly and send email to the support team that table is corrupted and > reapired automatically including the hostaname, and mysql version info. > I think about a perl script in cron job that do this. Is that the correct > way ?. Any ideas which is better to the perl system call to myisamchk or > 'REPAIR TABLE'...any ideas are appreciated ... > Peter > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
