It is possible to use MySQL databases as the target for the logs. LinkarWS will NOT install a MySQL database, it will have to be installed beforehand and the credentials provided in order to access it. These credentials will have to be parsed into the "Connection String" property.
In order to apply these changes they must first be saved via the "Save" button. The options that can be changed without having to restart LinkarWS are marked in green, any change to other options will require LinkarWS to be restarted.
When LinkarWS is started and MySQL logs are enabled it will try to connect with MySQL. If the database schema or table do not exist they will be created. When encountering any problems with the connection it is advised to enable "Serilog Debigging Mode" and analyze the "Serilog.LinkarServer.log" file for debugging.
After connecting to the database and creating the table an automatic script to delete old records will also be launched. This script will delete records older than 14 days by default. After changing any options a new script can be launched from a MySQL manager.
Script for old record deletion:
DROP EVENT IF EXISTS AutoDeleteOldLinkarServer;
CREATE EVENT AutoDeleteOldLinkarServer
ON SCHEDULE EVERY '1' DAY
STARTS '2026-01-01 00:00:00'
ON COMPLETION PRESERVE
DO
DELETE LOW_PRIORITY FROM linkarlogs.LinkarWS WHERE Timestamp < DATE_SUB(NOW(), INTERVAL 14 DAY);
Once the MySQL logs have been configured and LinkarWS is running any activity will start sending data to the log files. If the "Minimum Level" was configured to "Warning" data will only be logged when warnings or errors occur. You can test if the logging is working by setting the "Minimum Level" to "Information", which will log any operation to the database.
You can use any MySQL manager to view the log data. All the requests that reach LinkarWS end up as MV database accesses through LinkarServer. If an error occurs, and if the LinkarServer alarm system is configured, automatic emails will be sent with information about the problem. The content sent will include the "LkGuid" property which identifies the operation that caused the error. In order to troubleshoot the issue a query to locate the problematic record can be formed by using the "LkGuid". Queries can be run through the MySQL manager in order to cross-reference the log data from both the LinkarWS and the LinkarServer tables. In these cases queries such as the following can be run:
SELECT linkarlogs.LinkarWS.*, linkarlogs.LinkarServer.*
FROM linkarlogs.LinkarWS
INNER JOIN linkarlogs.LinkarServer ON linkarlogs.LinkarServer.LkGuid = linkarlogs.LinkarWS.LkGuid
WHERE linkarlogs.LinkarWS.LkGuid = "ad4d14b5-53e0-4829-b435-b5d981c4ba38";
