Managing Server Storage Capacity

Purpose

This article provides guidance on how to monitor and manage server storage capacity in Newired. It is especially relevant when the system indicates that storage usage is approaching its limit.

Running out of storage can lead to system instability, degraded performance, or data processing issues, particularly in Analytics.

How to Identify the Issue

Newired monitors server storage health and displays a warning banner in the Portal when storage usage exceeds a defined threshold (default 90%).

This warning indicates that immediate action is recommended to prevent further issues.

Storage health information is retrieved from the Newired Server via the endpoint:

<instance>/rest/app/diag

Configuring Storage Warning Threshold

The storage warning threshold is configurable.

• Default value: 90%

• Configuration property:

newired.storage.warning-threshold-percent=90

This property can be set in the newired.properties configuration file.

For more information on how to create and manage this configuration file, refer to:

https://support.newired.com/a/solutions/articles/103000012630

Recommended Actions

If storage capacity is nearing its limit, consider the following actions:

1. Configure Analytics Cleanup Job

The Analytics Cleanup Job helps reduce storage usage by removing historical analytics data based on defined retention rules.

This is typically the primary and safest way to free up space without impacting active system functionality.

Refer to the detailed configuration guide:

https://support.newired.com/a/solutions/articles/103000390833

2. Review and Remove Unused Published Content (Overlays)

Published content (Overlays) is stored on the server and can accumulate over time, especially in environments with frequent updates or testing.

Currently, there is no dedicated UI for managing or deleting published content, which may lead to uncontrolled growth of stored data.

Recommended approach:

• Review existing published content

• Identify obsolete or unused overlays

• Remove them from storage if no longer needed (with caution)

For context on publishing behavior, see:

https://support.newired.com/a/solutions/articles/103000012613

Note: Direct removal should be performed carefully and ideally with technical guidance to avoid unintended impact.

3. Additional Recommendations

• Regularly monitor storage growth trends

• Adjust data retention strategies where applicable

• Avoid unnecessary accumulation of test or temporary content