hcq/MaxScale
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

MXS-1344: Documentation update for MySQL Monitor and Binlog Server

Browse Source 
MXS-1344: Documentation update for MySQL Monitor and Binlog Server
This commit is contained in:
MassimilianoPinto
2017-08-23 16:41:32 +02:00
parent ad4e8dad94
commit 8285801fa6
2 changed files with 101 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
Documentation/Monitors/MySQL-Monitor.md
View File

@ -214,6 +214,16 @@ assigned the _Slave_ status which allows them to be used like normal slave
servers. When the option is disabled, the servers will only receive the _Slave
of External Server_ status and they will not be used.
## Using the MySQL Monitor With Binlogrouter
Since MaxScale 2.2 it's possible to detect a replication setup
which includes Binlog Server: the required action is to add the
binlog server to the list of servers only if _master_id_ identity is set.
For addition information read the
[Replication Proxy](../Tutorials/Replication-Proxy-Binlog-Router-Tutorial.md)
tutorial.
## Example 1 - Monitor script
Here is an example shell script which sends an email to an admin@my.org
@ -243,4 +253,4 @@ events=master_down,slave_down
```
When a master or a slave server goes down, the script is executed, a mail is sent and the administrator will be immediately notified of any possible problems.
This is just a simple example showing what you can do with MaxScale and monitor scripts.
This is just a simple example showing what you can do with MaxScale and monitor scripts.