[MXS-433] Improve logging Created: 2015-10-29  Updated: 2017-12-01  Resolved: 2015-12-03

Status: Closed
Project: MariaDB MaxScale
Component/s: Core
Affects Version/s: 1.3.0
Fix Version/s: 1.3.0

Type: New Feature Priority: Major
Reporter: Johan Wikman Assignee: Johan Wikman
Resolution: Fixed Votes: 0
Labels: None

Sub-Tasks:
Key
 Summary
 Type
 Status
 Assignee
MXS-434 General cleanup. Sub-Task Closed Johan Wikman  
MXS-435 Replace 4 files with 1. Sub-Task Closed Johan Wikman  
MXS-449 Replace logfiles with severities. Sub-Task Closed Johan Wikman  
MXS-453 Add LIST LOGS to maxadmin Sub-Task Closed Johan Wikman  
MXS-456 Log to shared memory or file. Sub-Task Closed Johan Wikman  
MXS-473 Replace all old logging calls with ne... Sub-Task Closed Johan Wikman  
MXS-474 Add printf checking. Sub-Task Closed Johan Wikman  

 Description   

The logging should be improvided; both how it is done from the code, but also how it is physically logged and the way it is represented.

In Amsterdam we agreed:

  • Have just 1 file.
  • Use syslog levels.
  • Look whether there is some 3rd-party library.
  • Is it really necessary with a non-blocking layer on top?
  • Clean up the interface.

 Comments   
Comment by Johan Wikman [ 2015-12-03 ]

The logging mechanism has now been heavily modified.

However, there are still other improvements to be made:

  • The logged message should contain a module part, indicating which module logged the message. There are e.g. many routers that may log the identical messages.
  • The responsibility for logging specific kind of messages should be cleared up. Can some error logging be centralized?
  • Error and notice messages should be cleaned up and be made end-user friendly.
  • etc.
Generated at Thu Feb 08 03:59:15 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.