S3 archive improvements and adding "Reindex" from S3
Scheduled Maintenance Report for Coralogix
The scheduled maintenance has been completed.
Posted May 27, 2020 - 13:13 IDT
We will be undergoing scheduled maintenance during this time.
Posted May 27, 2020 - 10:34 IDT
As part of our ROI vision, Coralogix is planning on improving its archive service and adding an option to trigger data reindexing straight from the Coralogix UI.
In order to do that, we are performing some changes in how the archive folders are created, this should not interfere with your work and wouldn't affect your current archive unless you have build anything on top of it that rely on the file name structure. This new change will now store delayed logs in the correct archive folder and not by their time of arrival to Coralogix.

Previous state:
Every log we received have been wrote to a file
If the file reached 100Mb or it’s last modified timestamp was 10 minutes ago -> The file is compressed to a file that it’s name was by the current timestamp
e.g. Coralogix/2020-05-07/12:00+00/12:49:30.676.csv.gz

New state:
Every log we received being written to a file with it’s related timeframe (Next nearest 10th minute) with additional uniq UUID
e.g. log with timestamp of 2020-05-07T12:49:30.676 will be written to 2020-05-07/12:00+00/12:50:00.000-41494f98-7b99-433e-a695-a59926b9a916.csv.gz
Posted May 26, 2020 - 11:00 IDT
This scheduled maintenance affected: Archiving.