Sensedia Analytics uses an automatic data rotation model to ensure performance, storage predictability, and compliance with the contracted retention period.
This model applies to the traces and calls indexes, each with specific rules for data rotation and deletion.
NOTEThe date calculation considers the GMT-0 time zone. For this reason, the daily index to be deleted may contain data from the previous day in local time.
The traces index is rotated on a monthly basis.
The deletion criteria always considers the oldest month available in the index.
By default, traces index data is retained for 90 days. When this limit is reached, the following behavior occurs:
The calls index is rotated according to the contracted retention period for Analytics.
Data deletion occurs daily and follows this criterion:
In both the traces and calls indexes, the rotation process uses GMT-0 as the calculation base.
This means that, depending on the local time, the index being removed may contain data from the previous day (in the case of calls) or the previous month (in the case of traces). This behavior is expected and does not indicate inconsistency or failure in the retention process.
The example below illustrates a scenario with 3-day retention, considering the execution of daily deletion after 00:00 (GMT-0).

Before the daily deletion, the system maintains the indexes corresponding to the last days within the configured retention period.
After the deletion process is executed, the index for the oldest day is removed, keeping only the most recent days within the retention window.
No. The rotation process is automatic and occurs continuously, respecting the retention rules configured for each index.
Deletion criteria are based exclusively on date and retention time, ensuring consistency in the data history available in Analytics.
We use cookies to enhance your experience on our site. By continuing to browse, you agree to our use of cookies.Learn more