Details
-
Type:
Task
-
Status: Open
-
Priority:
Trivial
-
Resolution: Unresolved
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
Description
I would like to suggest an improvement to the overall system to include an easily identifiable error code with all errors written to the error log, this currently seems to have a random feel to it.
Oracle database has the ORA- errors
SQL Server starts each line with Msg followed by a number and other information.
This would make identifying errors easier allowing errors to easily found in logs and if fed to the likes of Splunk allow other analysis to be done looking for incidents and repeat incidents in some cases.
The storage engines create a problem non existent in other databases which will need a resolution over the longer term either groupings of errors under the broader mariadb logging it the plugin vendors adopting the error logging style down into their code bases
This I don't see in the initial activity as a difficult task having only to make a suitable prefix and and the prefixed code into the text in mysqld_ername.h file in the text of every error code. I realise that this is not the solution but com_err needs to be altered to accommodate this change. That is a little more difficult.
Gliffy Diagrams
Attachments
Activity
- All
- Comments
- Work Log
- History
- Activity
- Transitions