Export - CSV (All fields)
Export - CSV (Current fields)
MXS-4788
Galeramon should use gtid_binlog_pos if gtid_current_pos is empty
Galeramon does not update replication lag of replicating serversMXS-1382
Use wsrep_sync_wait to detect replication lag in Galera clusters
Add support for pxc_maint_modeMXS-5096
Test and document the use of priorities for Galera Monitor switchover
Galera Monitor bootstrap command
Galera Monitor does not log an error if "SHOW SLAVE STATUS" fails
Semi automation of Galera recovery through GaleraMon
Add Galera DONOR & JOINER to state
Readwritesplit slave receiving alter requests
Allow priority definition for galera monitor nodes
Two monitors loaded at the same time result into not working installation
Allow GaleraMon to use a standalone slave as backup when entire cluster is down
Log server state changes
Add option to disallow server to ever be elected master
Using utf8mb4 on galera hosts stops maxscale connections
bugzillaId-672: "shutdown monitor" doesn't disconnect from backends
galera monitor node autodiscovery
Automatic discovery of Galera cluster
Update Galera Monitor discover-replicas to match the MariaDB Monitor version in functionality
Document that Galera Monitor requires REPLICA MONITOR grant
Show wsrep state details in galeramon diagnostic output
Maxscale monitor suddenly loses entire cluster status (galeramon)
Galeramon doesn't update GTID positions internally
Allow maintenance mode to be set on Galera cluster master
Galeramon doesn't work with max_slave_replication_lag
The 'INFORMATION_SCHEMA.SESSION_STATUS' feature is disabled; see the documentation for 'show_compatibility_56'
Crash in Galera monitor
Node wrongly in Maintenance, Running when the node is actually Down
Do not allow Galera master to be set to Drain
wsrep_desync behavior is undocumented
Master Stickiness status not displayed correctly with use_priority
Workaround Maxscale Not Distributing the load on all Galera Cluster nodes equally
Maxscale Not Distributing the load on all Galera Cluster nodes equally
Tmeout 600 seconds for Java application while connecting via MaxScale
Servers with priority=0 are selected as Master
Redirection of replication slaves to new master via galeramon
incorrect routing of selects with disable_master_failback
galeramon queries only status, not variables
Persistent connections prevents Galera node to stop/restart
Give a way to use slave_selection_criteria = LEAST_BEHIND_MASTER with Galera
The GTID of Galera Nodes is not displayed by maxctrl server list | maxscale 2.5.13
change in monitoring : add new status &/or unify mariadb & galeramon
Allow dirty reads/writes
Better handling for master's response (0xff) to COM_STMT_PREPARE
Lost connection to MySQL server during query
priority value ignored when a Galera node rejoins with a lower wsrep_local_index than current master
GaleraMon ignores server's SSL configuration
Galeramon: Server-side initiated maintenance mode
Unexpected internal state with ReadWriteSplit and proxy_protocol=true