Bug #46845 Allow custom scripts to be run when events are triggered for notification
Submitted: 20 Aug 2009 23:17 Modified: 14 Oct 2009 13:19
Reporter: Andy Bang Email Updates:
Status: Patch queued Impact on me:
None 
Category:MySQL Enterprise Monitor: Server Severity:S4 (Feature request)
Version:2.1.0.1093 OS:Any
Assigned to: Assigned Account CPU Architecture:Any
Triage: Needs Triage: D5 (Feature request) / R3 (Medium) / E6 (Needs Assessment)

[20 Aug 2009 23:17] Andy Bang
Description:
Several customers have asked that they be able to run a custom script when events are triggered.  For example, if the Enterprise Monitor detects that a slave has stopped replicating, these customers would like to run a script to open a ticket in their trouble tracking system (in addition to the email and SNMP notifications that are already available).  Or, rather than using the Monitor's email alerts, they would use the script to generate alerts in their own notification system, which may have better knowledge of who to handle the problem, when they're on vacation (i.e. to notify someone else), and who to escalate things to if the problem isn't resolved quickly.

How to repeat:
N/A

Suggested fix:
Allow customers to specify how to run a script (e.g. "usr/bin/perl") and what script to execute (e.g. "createTicket.pl"), then call that script when an alert is triggered (i.e. when we would currently send an email or generate an SNMP trap), passing various parameters to the script (e.g. rule name, alert level, type of alert, server affected, etc).
[14 Oct 2009 13:19] Enterprise Tools JIRA Robot
Sloan Childers writes: 
trouble ticket integration/sendmail patch pushed to /etools/branches/script-notify