[MXS-2692] Monitor of binlog router Created: 2019-09-20  Updated: 2020-09-28  Resolved: 2020-09-24

Status: Closed
Project: MariaDB MaxScale
Component/s: binlogrouter
Affects Version/s: 2.3.12
Fix Version/s: 2.5.4

Type: New Feature Priority: Major
Reporter: Sebastien GIRAUD Assignee: Esa Korhonen
Resolution: Fixed Votes: 2
Labels: Monitoring
Environment:

Debian Linux MaxScale1 4.9.0-9-amd64 #1 SMP Debian 4.9.168-1+deb9u3 (2019-06-16) x86_64 GNU/Linux

Epic Link: Pinloki Project
Sprint: MXS-SPRINT-114, MXS-SPRINT-115

 Description   

Hi,

In order to be able to monitor MaxScale binlogrouter, is it possible to manage the monitoring in order to view the activity of binlogrouter directly in maxctrl command ?

Thanks



 Comments   
Comment by Sylvain ARBAUDIE [ 2019-09-20 ]

when we tried this configuration : 

 
 
[binlog-router]
 
type=server
 
address=127.0.0.1
 
port=5308
 
protocol=MariaDBBackend
 
 
 
[replication-monitor]
 
module=mariadbmon
 
type=monitor
 
servers=galera1,galera2,galera3,binlog-router
 
servers=galera1,galera2,galera3,primary1
 
user=maxscale
 
password=M4xscale_pw
 
monitor_interval=500
 
 
 
[Replication]
 
type=service
 
router=binlogrouter
 
#version_string=5.6.17-log
 
user=maxscale
 
passwd=M4xscale_pw
 
router_options=server_id=3,user=maxscale,password=M4xscale_pw,master-id=1,heartbeat=30,binlogdir=/var/binlogs,transaction_safety=1,master_version=5.6.19-common,master_hostname=common_server,mariadb10-compatibility=1
 
 
 
[Replication Listener]
 
type=listener
 
service=Replication
 
protocol=MySQLClient
 
port=5308

we had this error message in the maxscale logs : 

2019-09-20 15:11:19   error  : (7) Unexpected query from ‘maxscale’@‘::ffff:127.0.0.1’: SHOW SLAVE STATUS;
 
2019-09-20 15:11:19   error  : (7) Unexpected query from ‘maxscale’@‘::ffff:127.0.0.1’: SHOW SLAVE STATUS;
 
2019-09-20 15:11:20   error  : (7) Unexpected query from ‘maxscale’@‘::ffff:127.0.0.1’: SHOW SLAVE STATUS;
 
2019-09-20 15:11:20   error  : (7) Unexpected query from ‘maxscale’@‘::ffff:127.0.0.1’: SHOW SLAVE STATUS;

Comment by Sylvain ARBAUDIE [ 2019-09-20 ]

i can only guess it might be linked to Markus coments today on slack that maxscale tends to perform too many litterals comparisonswhen trying to interpret command lines.

Generated at Thu Feb 08 04:15:59 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.