RoboServer Log Database
This is the logging database used by the Management Console to store schedule runs, schedule messages, robot runs, robot messages, robot tags, Desktop Automation Service messages as well as all RoboServers belonging to clusters where database logging has been enabled in the cluster settings. The database is configured in the same way as the cluster databases.
The following cleanup thresholds can be configured for the RoboServer log database.
|
Property |
Description |
|---|---|
|
Keep robot and schedule statistics for (day) |
Specify the number of days to keep the robot and schedule statistics. According to the cleanup settings you define, the old data is deleted on a daily basis. |
|
Max messages in robot run |
Specifies the maximum number of messages in a single robot run. The robot message logging stops for the specific run when the number of robot messages exceeds this threshold. The cleanup deletes the oldest robot runs and the messages for the deleted runs. If you experience performance problems with the log database, you can lower this threshold. To store more historic messages, you can increase this threshold. |
To use a database for logging, you must prepare your database server by either creating a new database (schema), or simply making sure an existing database is available. You must obtain a username and password with rights to create tables, drop tables, create indexes, drop indexes, select, insert, update, and delete in the database.
Both the Management Console and RoboServer will create the log tables automatically when they are started (if the tables do not already exist). However, you may also create them using the Scripts for Creating Database Tables.