This page is part of MariaDB's MariaDB Documentation.
The parent of this page is: Log Archive
Topics on this page:
Error Logs record important database server output related to configuration and operation.
Despite being called "error logs", these logs typically contain both data related to errors and data which does not represent an error. The log is so named because this output is sent to
stderr (standard error).
Single Node Analytics
Single Node Transactions
This parameter can be set in Configuration Manager.
After a configuration has been prepared with the intended parameters, it must be applied to the desired service for this change to take effect.
The service will be restarted when the configuration is applied.
Error Log data is available in the Log Archive.
To download log data:
Log in to the MariaDB SkySQL portal.
Access "Monitoring" in left navigation.
From SkySQL Monitoring, access "Logs" in left navigation.
Select the desired server(s), log types (such as "Error Log"), and time frame, then click the "Download" button to download the logs.
Log files can be downloaded in your choice of JSON and/or plain text formats.
.ziparchive will contain one file per server, log, day, and format.
The Log Archive retains log data for 7 years. Data is retained even if the SkySQL service is deleted.
Logs are stored in GCS buckets with HTTPS data-in-transit encryption and Google default (AES256) data-at-rest encryption.
Logs are stored by day, by service, by server, by log type.
To request log data expungement, submit a Support Request.
Data retention requirements vary by business. A business process may be needed to download error log data in support of your data retention requirements.
Error log lines vary in structure and content.
Most rows include as a first field the date in YYYY-MM-DD format.
Most rows state precedence of error, warning, or note.
When downloaded in plain text format, Error Log data is as outputted by the database server.
When downloaded in JSON format, Error Log data has this format for each line, incorporating the plain text format:
One JSON object is produced for each logical line from the original plain text log file.
JSON key order is not guaranteed.