Internal documentation only
This page has been marked as draft.
Possible caveats for shortening the retention period of database against the default settings
The possible caveats for this would be:
- Loss of Historical Data
- Short retention period limits the ability to perform long-term trend analysis. If the client wants to minimize the value of the retention period like 96 hours I guess it would not have much of an impact.
In addition, OP5 Monitor comes with a default database retention period of 192 hours, which is 8 days. This is designed to be sufficiently short to not require too much disk space while keeping enough data to allow you to evaluate storage requirements and determine suitable retention times. OP5 Monitor self-monitoring is enabled during installation and warns you if the server is running out of disk space.
Specifically the “Configure Logger” section – you can configure for how long you want to keep collected logs in the database, and then either delete them or move them to files on disk.
Setting the retention time for example to 1 hour will rotate out the existing data and free up disk space.
The setting is possible to change from CLI as well by following the guide below:
Open a SSH connection to the op5 server you want to change the setting on
Open the postgresql command line:
psql -U op5lsu op5lsu Run the following query to set how many days the logs should be kept in DB: op5lsu=# UPDATE settings SET keep_in_db = 1;
This will reduce the time how long the logs are kept in the database to one hour.
Exit the postgresql cli op5lsu-# \q
Restart the postgresql service service postgresql restart Repeat the above on all nodes that you would like to change to 1 hour retention time in the database.
However, I would recommend increasing the disk space of the server to mitigate issues with the disk being filled up.
Please refer to this document for more information about Manage logging. https://docs.itrsgroup.com/docs/op5-monitor/current/topics/configure/logging.html#Configure_Logger_in_OP5_Monitor