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

MXS-1736 Clarify MaxInfo tutorial

Browse Source
This commit is contained in:
Johan Wikman
2018-08-07 12:51:09 +03:00
parent 94994268bd
commit 974bf3c115
1 changed files with 7 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
Documentation/Tutorials/MaxScale-Information-Schema.md
View File

@ -31,7 +31,7 @@ to localhost as well.
type=service type=service
router=maxinfo router=maxinfo
user=monitor user=monitor
passwd=EBD2F49C3B375812A8CDEBA632ED8BBC passwd=my_secret
``` ```
The listener section defines the protocol, port and other information needed The listener section defines the protocol, port and other information needed
@ -39,6 +39,10 @@ to create a listener for the service. To listen on a port using the MySQL
protocol a section as shown below should be added to the configuration protocol a section as shown below should be added to the configuration
file. file.
In this example we use a cleartext password `my_secret`. For increased
security the password can be encrypted as explained
[here](../Getting-Started/Configuration-Guide.md#encrypting-passwords).
``` ```
[MaxInfo Listener] [MaxInfo Listener]
type=listener type=listener
@ -83,9 +87,9 @@ MySQL status and ping requests. These may be used for simple monitoring of
MariaDB MaxScale. MariaDB MaxScale.
``` ```
% mysqladmin -hmaxscale.mariadb.com -P9003 -umonitor -pxyz ping % mysqladmin -hmaxscale.mariadb.com -P9003 -umonitor -pmy_secret ping
mysqld is alive mysqld is alive
% mysqladmin -hmaxscale.mariadb.com -P9003 -umonitor -pxyz status % mysqladmin -hmaxscale.mariadb.com -P9003 -umonitor -pmy_secret status
Uptime: 72 Threads: 1 Sessions: 11 Uptime: 72 Threads: 1 Sessions: 11
% %
``` ```