diff options
| author | Igor Pashev <pashev.igor@gmail.com> | 2016-06-27 03:51:58 +0800 |
|---|---|---|
| committer | Igor Pashev <pashev.igor@gmail.com> | 2016-06-27 17:15:41 +0800 |
| commit | a1617ebaeb256b3d359cc9fe389b8001235100c2 (patch) | |
| tree | 4d7bcaf69b2987b333e52b072c08f4cb8230641e /README.md | |
| parent | 54f6dfb100d5ad817898d3f7cb13028b91bdecaf (diff) | |
| download | mywatch-a1617ebaeb256b3d359cc9fe389b8001235100c2.tar.gz | |
Allow killing queries
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 21 |
1 files changed, 16 insertions, 5 deletions
@@ -1,8 +1,8 @@ My Watch ======== -HTTP server for viewing MySQL queries on multiple servers. Designed to work -behind [Sproxy](https://github.com/zalora/sproxy). +Web application for viewing and killing MySQL queries on multiple +servers. Designed to work behind [Sproxy](https://github.com/zalora/sproxy). Requirements @@ -66,10 +66,21 @@ user = user2 ``` -Database Privileges -=================== +Database Configuration +====================== -MyWatch needs the `PROCESS` privilege. +MyWatch needs the [PROCESS](http://dev.mysql.com/doc/refman/en/privileges-provided.html#priv_process) +privilege. + +To be able to kill queries a procedure named `mywatch_kill` must exist +in the `mysql` database. MyWatch invokes `CALL mysql.mywatch_kill(id)` +for killing queries. It's up to you how to implement this routine, for a +safe example see [sql/mywatch_kill.sql](sql/mywatch_kill.sql). Of cource, +MyWatch should be granted to execute this procedure. If this procedure +does not exist, MyWatch will not show this possibility in user interface, +API will work, but result in Internal Server Error (HTTP 500). There is no +filtering at application level, though the "kill" button may not be shown +in some circumstances. Screenshots |