Storage Capacity and Retention Policies
Edge-EMS Builder estimates storage sustainability from actual database usage, compression, and recent growth, recommending retention periods to balance historical depth against available disk space.
What to check first
Section titled “What to check first”- Host resources: CPU, memory, disk utilization, and archive reminders.
- Growth and compression: evaluate daily growth using physical storage usage before and after compression.
- Safety margin: retain necessary free space and estimate when high-watermark cleanup may be triggered.
- Retention recommendations: increase, maintain, or reduce retention for raw data, aggregation data, shared data, trigger records, alarm records, and MQTT records.
Estimates depend on current samples and runtime load. Reassess after changes to device counts, sampling frequency, or scripts. Recommendations do not automatically change retention policies.
Apply recommendations
Section titled “Apply recommendations”- Review current retention periods and capacity estimates.
- Verify that data requiring retention is protected by archiving.
- After administrator confirmation, submit all six policies together.
- Read back configuration and continue monitoring growth and archive status.
Batch updates run in one transaction to prevent partial updates. Shortening retention may delete history; extending retention does not restore deleted data.
Integration APIs
Section titled “Integration APIs”| Information or operation | API |
|---|---|
| Host resources | GET /system/resources |
| Storage assessment | GET /system/storage-capacity-estimate |
| Current retention policies | GET /ems-data/retention |
| Atomically update all six policies | POST /ems-data/update/retention/batch |
The request’s retentionPolicies must cover all six categories. Use table names and parameters returned by the current API rather than guessing the schema. Use the system maintenance Skill to analyze recommendations and establish Periodic archiving.