[MXS-4480] Make it possible to focus debug/info logging to a specific part of MaxScale Created: 2023-01-19 Updated: 2023-12-15 |
|
| Status: | Open |
| Project: | MariaDB MaxScale |
| Component/s: | Core |
| Affects Version/s: | None |
| Fix Version/s: | Icebox |
| Type: | Task | Priority: | Major |
| Reporter: | markus makela | Assignee: | Joe Cotellese |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Description |
|
This would make the info log a more useful tool for figuring out why something isn't working as expected. Some work on this feature has already been implemented in older releases with the support for service-level and session-level logging as well as the support of syslog facilities for certain types of messages. An improvement would be to further filter the logging by only doing it for certain parts of the system, for example on a per module basis. |
| Comments |
| Comment by Johan Wikman [ 2023-01-19 ] |
|
The information needed for filtering is already present. When any of the MXB_(DEBUG|INFO|...) logging macros are used, the module name is passed to mxb_log_message(...) that does the actual logging. Thus, all that is needed is to add some mechanism using which it can be specified e.g. that debug messages generated by module X should be logged. |