Scheduled - 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.

Summary:
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
May 26, 11:00 IDT

Scheduled - As a preparation for a major improvement in our immediate alerting mechanism. The Coralogix team will be performing an upgrade that will replace some of our key alerting components. Even though we are expecting no impact to our customers, during the upgrade timeframe, there is a low probability that we may experience unexpected results in alerting. This status will be reminded before, during, and after the upgrade is completed. We advise to take that into account on your on-call procedures.
May 24, 21:36 IDT