Conversation
csc-nelli
changed the title
csc-nelli
changed the title
oscarkraemer
left a comment
oscarkraemer
left a comment
There was a problem hiding this comment.
IMO it would be worth to move the different topics to other existing files / paths.
| - MariaDB: | ||
| - Error log: cloud/dbaas/perftune-mariadb-errorlog.md | ||
| - PostgreSQL: | ||
| - Importance of PostgresSQL log: cloud/dbaas/perftune-postgresql-log.md |
There was a problem hiding this comment.
Should these new entries be under Pukki/Databases/MariaDB and Pukki/Databases/PostgreSQL instead of Pukki/Common Performance issues ?
Also the sections for MariaDB and PostgreSQL have different names Error log and Importance of PostgreSQL log should they have similar names? Also the file names are a bit different.
|
|
||
| Access the Web UI in [https://pukki.dbaas.csc.fi/project](https://pukki.dbaas.csc.fi/project), click the `instance name` and go to `logs` tab. | ||
|
|
||
| **Note:** If log lines are with same `timestamp` then log lines may be displayed in bit of a mixed order. |
There was a problem hiding this comment.
The sections How to access database logs is basically the same in PostgreSQL and MariaDB. Maybe it should be documented in More advanced features or somewhere under Getting started with DBaaS
| +--------------------------------------+---------------------------+------------+-------------------+--------+------------------+--------+----------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------------------------+------+------+ | ||
| | ID | Name | Datastore | Datastore Version | Status | Operating Status | Public | Addresses | Flavor ID | Size | Role | | ||
| +--------------------------------------+---------------------------+------------+-------------------+--------+------------------+--------+----------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------------------------+------+------+ | ||
| | 0a8b6df2-140d-4932-b477-b3d3a881fecf | mariadb-12-12-14:03:13 | mariadb | 11.4.8 | ACTIVE | HEALTHY | True | [{'address': '192.168.240.106', 'type': 'private', 'network': '51e07f88-483a-4aaf-a349-2277f6afaabe'}, {'address': '195.148.20.137', 'type': 'public'}] | d4a2cb9c-99da-4e0f-82d7-3313cca2b2c2 | 1 | | |
There was a problem hiding this comment.
I'm usually avoiding showing public IP addresses and UUIDs in the documentation. In Command Line tools section there are examples how we have documented this so far.
| * **Aborted connection:** Usually these are connections timing out due to inactivity. There is a possibility that network connection between application and database has been interrupted during transaction, causing resource intesive rollback, so these cannot be completely ignored either. | ||
| * **Access denied:** Maybe someone authorized was trying manually to connect to the database or maybe it is some background job failing to connect, which effects was not visible. Consider these also to be possible break-in attempts. | ||
|
|
||
| Any other message that requires attention (including `note` and `warning` level messages) are usually related to performance of the database. |
There was a problem hiding this comment.
IMO this file should be under Databases/MariaDB
|
|
||
| PostgreSQL server log gives important information from the database's current health and operation. | ||
|
|
||
| ## How to access database logs |
There was a problem hiding this comment.
How to access database logs, could be under some other topic.
Same as MariaDB "the logs example" could be under Databases/PostgreSQL
| ``` | ||
|
|
||
| **Note:** In Pukki `max_wal_size` is tied to instance's flavor size | ||
|
|
There was a problem hiding this comment.
Maybe worth mention that this log entries might happen when upgrading the database verison or if one does manually run reindexing.
|
|
||
| ## How to access database logs | ||
|
|
||
| **Note:** If the system does not return any log lines in either methods then that means there are no log entries within the 1 month retention period which is common to MariaDBs. |
There was a problem hiding this comment.
Maybe add that if there are no logs visible but you think there should be they can always contact service-desk
| 2026-01-30T14:58:32.882788932+00:00 stderr F 2026-01-30 14:58:32.882 UTC [64] ERROR: syntax error at or near "test" at character 8 | ||
| 2026-01-30T14:58:32.882788932+00:00 stderr F 2026-01-30 14:58:32.882 UTC [64] STATEMENT: CREATE test AS SELECT GENERATE_SERIES(1,500000) AS id, MD5(RANDOM()::TEXT) AS random_text; | ||
| ``` | ||
|
|
There was a problem hiding this comment.
Are there any specific logs that happens when doing Pukki operations like upgrade, resize, enable root, create database a.s.o. that could be interesting to document?
csc-nelli
changed the title
2 participants
Proposed changes
I don't know any qualified person with write access to review this, so as long as formatting looks good, then DBaaS team can internally suggest changes to next version.
As part of umbrella task I started documenting common DB performance issues from server logging sections;
Postgres: preview page
MariaDB: preview page
Checklist before requesting a review