Storage
On this page
The Storage page configures how long the project retains historical data. Retention policies apply independently to alarm history and operator intervention logs — each has its own configurable period that controls when old records are automatically purged.
Retention policies
Retention periods are set in the format Xy Xm Xd Xh (years, months, days, hours). When a record’s age exceeds the configured limit, it is automatically removed, keeping disk usage bounded over time.
Alarm history retention is configured in Settings → General under the Alarms section. Operator intervention log retention is configured in the same page under the User interventions section. Both default to 1y 0m 0d 0h (one year).
Adjusting retention
To change a retention period, navigate to Settings → General, expand the relevant section (Alarms or User interventions), and update the Storage field with the new duration.
Shortening a retention period takes effect immediately — records older than the new limit are purged at the next cleanup cycle.
Longer retention periods give operators more historical context when investigating past events, but they increase the amount of data stored on disk. Set retention to match your operational requirements and the available storage capacity on the server.
Records deleted by the retention policy are permanently removed. If long-term archiving is required, export or back up historical data before the retention limit is reached.