[MXS-1954] Explain why servers change state Created: 2018-07-03 Updated: 2024-01-04 Resolved: 2020-02-11 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | mariadbmon |
| Affects Version/s: | None |
| Fix Version/s: | 2.5.0 |
| Type: | New Feature | Priority: | Minor |
| Reporter: | markus makela | Assignee: | Esa Korhonen |
| Resolution: | Fixed | Votes: | 1 |
| Labels: | None | ||
| Epic Link: | Monitor Improvements |
| Sprint: | MXS-SPRINT-99 |
| Description |
|
When a server changes state, it should always be accompanied with a message explaining why the state changed. For example, if a server loses the slave status a log message should be logged before the state change message is logged. Similarly for masters being set into read-only mode, a message stating that a master transitioned into read-only mode should be logged. |
| Comments |
| Comment by Esa Korhonen [ 2020-02-11 ] |
|
Only partially done. |