Skip to content
This repository has been archived by the owner on Sep 30, 2024. It is now read-only.

Improve logging of problems during db connection #1488

Open
kamil-holubicki opened this issue Jun 7, 2023 · 0 comments
Open

Improve logging of problems during db connection #1488

kamil-holubicki opened this issue Jun 7, 2023 · 0 comments

Comments

@kamil-holubicki
Copy link

Some error logs indicate only the error returned by the server without
the information about the server identity itself.
On the other hand, there are also logs which display the server identity
together with the returned error.

Example:

2022-03-30T08:59:22.718093+02:00 orchestrator123.prod.com orchestrator[39052]: 2022-03-30 08:59:22 ERROR Error 3884: Storage engine could not allocate temporary tablespace for this session.

There is no way to identify which MySql server causes problems.

On the other hand sometimes there are logs which provide full context:

2022-03-30T09:49:03.634230+02:00 orchestrator123prod.com orchestrator[39052]: 2022-03-30 09:49:03 ERROR ReadTopologyInstance(mysqlserver-321.prod.com:3306) show global status like 'Uptime': Error 3884: Storage engine could not allocate temporary tablespace for this session.

Error logs should be consistent.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant