[MDEV-22208] Allow "alert" script to be executed when errors or warnings are logged Created: 2020-04-10  Updated: 2020-08-25  Resolved: 2020-04-10

Status: Closed
Project: MariaDB Server
Component/s: OTHER
Fix Version/s: 10.1.0

Type: Task Priority: Major
Reporter: Chris Calender (Inactive) Assignee: Unassigned
Resolution: Not a Bug Votes: 0
Labels: None


 Description   

It would be a very useful feature if MaxScale could allow an "alert" script to be executed anytime errors or warnings are logged.

The more granular this would be, the better (perhaps it could be a comma-delimited list of error/warning code values).

To give an example, someone wants to be able to be notified immediately, via a script from MaxScale, when they see the following error ("Too many connections"):

2020-04-01 10:00:01 error : Unable to write to backend 'server1' due to authentication failure. Server in state RUNNING SLAVE.
2020-04-01 10:00:01 error : (661327) Invalid authentication message from backend 'server1'. Error code: 1040, Msg : #08004Too many connections



 Comments   
Comment by Chris Calender (Inactive) [ 2020-04-10 ]

Sorry, I meant for this to be an MXS bug. I've filed the MXS Jira issue, and am closing this one.

Generated at Thu Feb 08 09:13:01 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.