Improve logging
(MXS-433)
|
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | Core |
| Affects Version/s: | None |
| Fix Version/s: | 1.3.0 |
| Type: | Sub-Task | Priority: | Major |
| Reporter: | markus makela | Assignee: | Johan Wikman |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Description |
|
Currently the only way to see which logs are enabled is to look at the log files. There could be a maxadmin command which prints the locations and states of each log file. |
| Comments |
| Comment by Johan Wikman [ 2015-11-05 ] |
|
In an 1.3.0 context this doesn't really make sense, since there will be just one file. What could make sense is to be able to query what syslog priority levels are enabled. |
| Comment by Johan Wikman [ 2015-12-03 ] |
|
So, in principle this is reasonable, but for the fact that there no longer are any log files. The same mechanism for showing what log priorities are enabled would make sense. However, this is actually a bigger issue. The maxadmin interface should get an overhaul; whatever you can update, you should be able to read and that should be implemented in a consistent manner all across the entire maxadmin. |
[MXS-453]