Completed -
The scheduled maintenance has been completed.
Dec 20, 19:00 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Dec 16, 07:00 UTC
Scheduled -
As part of our effort to make our platform more stable , we are planning to upgrade our infrastructure components. This upgrade is expected to last approximately 108 hours. The upgrade will take place on cx_id (us2) , cx_env_id (cx498) , cx_region (aws-us-west-2)
*Possible Components Affected - ALL*
There might be some impact on customers during this upgrade, if you experience any unusual behavior please reach out to our 24/7 chat support or your dedicated TAM
Dec 12, 10:26 UTC
Completed -
The scheduled maintenance has been completed.
Dec 18, 18:00 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Dec 18, 09:00 UTC
Scheduled -
As part of our ongoing effort to improve archive search performance and efficiency, we are introducing changes to the S3 bucket permissions needed for the logs/Traces S3 bucket. These changes will allow us to compact log and trace archive files, resulting faster query times and slightly smaller storage footprint. The update will take effect on December 16th, 2024.
Who is this relevant for? This change applies to any Coralogix customer that uses Coralogix’s archive feature for logs and/or traces stored in S3. Since this is one of the core components in Coralogix most customers will need to update the permissions.
What is happening? On December 16th, 2024, Coralogix will introduce a new compaction method for the archive files for Logs and Traces stored in S3 bucket. This means that files will be consolidated. Compaction will happen only once, on new files, every 20 minutes or once the total size of them reaches a size of 1GB (according to the earlier). Coralogix will need new permissions to enable file compaction.
What should you do? To benefit from these improvements, please update your S3 bucket permissions by December 16th, 2024. Add the following permissions to the S3 bucket: s3:DeleteObject, s3:DeleteObjectVersion, s3:DeleteObjectTagging, s3:DeleteObjectVersionTagging We’ve updated our CloudFormation templates and tutorials to assist you in making these changes.
Why do you need all those permissions? s3:DeleteObject – Allows deleting objects from the S3 bucket. s3:DeleteObjectVersion – Allows deleting all versions of an object when bucket versioning is enabled. Object cannot be deleted when they have versions. s3:DeleteObjectTagging – Allows deleting tags from an object (used by the Archive retention feature). Object cannot be deleted when they are tagged. s3:DeleteObjectVersionTagging – Enables deleting tags for a versioned object.
Why is this change being made? This update is designed to enhance both storage efficiency and system performance:
Important for ETL users: If you run ETL processes or any other scripts querying your S3 bucket, you will need to adapt the process to extract according to the following logic: If you granted Coralogix PutObjectTagging permissions: Extract only files with the following tag value: CX_COMPACTION_LEVEL:2. In case you did not grant PutObjectTagging permissions: You should refrain from querying files from the last 20 minutes as they will be compacted.
What happens if you don’t update? If the S3 permissions are not updated, we will implement a workaround that replaces compacted log files with zero-byte files in your bucket. Although this workaround reduces storage, it is less efficient and may incur minor costs related to PUT objects.
Completed -
The scheduled maintenance has been completed.
Dec 17, 18:06 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Dec 17, 09:06 UTC
Scheduled -
As part of our ongoing effort to improve archive search performance and efficiency, we are introducing changes to the S3 bucket permissions needed for the logs/Traces S3 bucket. These changes will allow us to compact log and trace archive files, resulting faster query times and slightly smaller storage footprint. The update will take effect on December 16th, 2024.
Who is this relevant for? This change applies to any Coralogix customer that uses Coralogix’s archive feature for logs and/or traces stored in S3. Since this is one of the core components in Coralogix most customers will need to update the permissions.
What is happening? On December 16th, 2024, Coralogix will introduce a new compaction method for the archive files for Logs and Traces stored in S3 bucket. This means that files will be consolidated. Compaction will happen only once, on new files, every 20 minutes or once the total size of them reaches a size of 1GB (according to the earlier). Coralogix will need new permissions to enable file compaction.
What should you do? To benefit from these improvements, please update your S3 bucket permissions by December 16th, 2024. Add the following permissions to the S3 bucket: s3:DeleteObject, s3:DeleteObjectVersion, s3:DeleteObjectTagging, s3:DeleteObjectVersionTagging We’ve updated our CloudFormation templates and tutorials to assist you in making these changes.
Why do you need all those permissions? s3:DeleteObject – Allows deleting objects from the S3 bucket. s3:DeleteObjectVersion – Allows deleting all versions of an object when bucket versioning is enabled. Object cannot be deleted when they have versions. s3:DeleteObjectTagging – Allows deleting tags from an object (used by the Archive retention feature). Object cannot be deleted when they are tagged. s3:DeleteObjectVersionTagging – Enables deleting tags for a versioned object.
Why is this change being made? This update is designed to enhance both storage efficiency and system performance:
Important for ETL users: If you run ETL processes or any other scripts querying your S3 bucket, you will need to adapt the process to extract according to the following logic: If you granted Coralogix PutObjectTagging permissions: Extract only files with the following tag value: CX_COMPACTION_LEVEL:2. In case you did not grant PutObjectTagging permissions: You should refrain from querying files from the last 20 minutes as they will be compacted.
What happens if you don’t update? If the S3 permissions are not updated, we will implement a workaround that replaces compacted log files with zero-byte files in your bucket. Although this workaround reduces storage, it is less efficient and may incur minor costs related to PUT objects.
Completed -
The scheduled maintenance has been completed.
Dec 16, 17:34 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Dec 16, 12:34 UTC
Scheduled -
As part of our ongoing commitment to improving performance and reliability, we are implementing enhancements to our Events2Metrics (E2M) infrastructure.
While we do not anticipate delays in metric alerts derived from E2M (log2metric or trace2metric), there is a small possibility that some alerts may experience delays during the update process. Please be assured that we are closely monitoring this transition to ensure minimal impact.
If you have any questions or encounter unexpected behavior, our support team is here to assist you promptly.
Dec 16, 12:32 UTC
Completed -
The scheduled maintenance has been completed.
Dec 16, 17:00 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Dec 16, 08:00 UTC
Scheduled -
As part of our ongoing effort to improve archive search performance and efficiency, we are introducing changes to the S3 bucket permissions needed for the logs/Traces S3 bucket. These changes will allow us to compact log and trace archive files, resulting faster query times and slightly smaller storage footprint. The update will take effect on December 16th, 2024.
Who is this relevant for? This change applies to any Coralogix customer that uses Coralogix’s archive feature for logs and/or traces stored in S3. Since this is one of the core components in Coralogix most customers will need to update the permissions.
What is happening? On December 16th, 2024, Coralogix will introduce a new compaction method for the archive files for Logs and Traces stored in S3 bucket. This means that files will be consolidated. Compaction will happen only once, on new files, every 20 minutes or once the total size of them reaches a size of 1GB (according to the earlier). Coralogix will need new permissions to enable file compaction.
What should you do? To benefit from these improvements, please update your S3 bucket permissions by December 16th, 2024. Add the following permissions to the S3 bucket: s3:DeleteObject, s3:DeleteObjectVersion, s3:DeleteObjectTagging, s3:DeleteObjectVersionTagging We’ve updated our CloudFormation templates and tutorials to assist you in making these changes.
Why do you need all those permissions? s3:DeleteObject – Allows deleting objects from the S3 bucket. s3:DeleteObjectVersion – Allows deleting all versions of an object when bucket versioning is enabled. Object cannot be deleted when they have versions. s3:DeleteObjectTagging – Allows deleting tags from an object (used by the Archive retention feature). Object cannot be deleted when they are tagged. s3:DeleteObjectVersionTagging – Enables deleting tags for a versioned object.
Why is this change being made? This update is designed to enhance both storage efficiency and system performance:
Important for ETL users: If you run ETL processes or any other scripts querying your S3 bucket, you will need to adapt the process to extract according to the following logic: If you granted Coralogix PutObjectTagging permissions: Extract only files with the following tag value: CX_COMPACTION_LEVEL:2. In case you did not grant PutObjectTagging permissions: You should refrain from querying files from the last 20 minutes as they will be compacted.
What happens if you don’t update? If the S3 permissions are not updated, we will implement a workaround that replaces compacted log files with zero-byte files in your bucket. Although this workaround reduces storage, it is less efficient and may incur minor costs related to PUT objects.
Resolved -
This incident has been resolved.
Dec 15, 14:03 UTC
Investigating -
Our team is currently investigating an issue with delays in metric ingestion for some customers. Metrics may not appear in dashboards in real-time, as well as metric alerts triggering with some delay or possible false positives. The issue is under investigation, and we are working on a solution
For further assistance, please reach out via our in-app chat or email us
Dec 15, 13:35 UTC
Resolved -
This incident has been resolved.
Dec 14, 04:14 UTC
Monitoring -
A fix has been implemented and we are monitoring the results. Queries in All Logs appear functional now and should not return errors.
Dec 14, 03:35 UTC
Update -
We are continuing to investigate this issue.
Dec 14, 02:54 UTC
Investigating -
Our team is currently investigating an issue that affects querying data from "All Logs" This issue affects customers who store their data on our US1 region (team.coralogix.us).
Dec 14, 01:40 UTC
Completed -
The scheduled maintenance has been completed.
Dec 11, 10:30 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Dec 11, 08:30 UTC
Update -
We will be undergoing scheduled maintenance during this time.
Dec 10, 13:26 UTC
Scheduled -
As part of the recent infrastructure upgrades to our alerting system, we identified an issue related to the representation of flow alerts on the incidents screen. Please note that the flow alerts themselves are functioning as expected and triggering normally; however, the data representation in the incidents view may be temporarily misleading due to a cache issue.
To resolve this, we will be performing a cache reset across all regions. This may result in a brief delay in the updates to the incidents screen, but it will not affect the actual triggering of flow alerts.
Impact: - No impact on alert triggering: Flow alerts are being triggered normally. - Possible temporary lag in the representation of alerts in the incidents screen during the cache reset.
We are actively working to resolve this issue and ensure accurate data representation. We appreciate your understanding and patience as we work through this. Should you have any concerns, our support team is available 24/7 to assist.
Dec 10, 13:25 UTC
Completed -
The scheduled maintenance has been completed.
Dec 9, 14:52 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Dec 9, 09:04 UTC
Update -
We will be undergoing scheduled maintenance during this time.
Dec 8, 09:11 UTC
Scheduled -
As part of our ongoing commitment to enhance the flexibility of our monitoring capabilities, the alerting mechanism will go through maintenance work.
What is happening? We are about to upgrade the infrastructure supporting our alerting mechanism to enhance its capabilities.
When? Wednesday, December 4th - Sunday, December 8h.
Where? The rollout will happen one environment at a time. Out team will evaluate the rollout before continuing to the next env and will follow the following schedule: EU1 environment - *team*.coralogix.com US1 environment - *team*.app.coralogix.us US2 environment - *team*.app.cx498.coralogix.com
Was this upgrade tested? Since alerting is a crucial part of our solution our team has conducted rigorous testing prior to this maintenance process across a broad range of alert types and our outgoing webhooks integrations.
What can go wrong? As with any infrastructure maintenance, there is always the potential for unforeseen issues. Should there be issues, you may expect brief delays in triggering of some alerts. We will monitor the systems behaviour and are making every effort to minimize any disruptions
Feel free to reach out to our dedicated in-app Support team is available 24/7 to provide immediate assistance and resolve any issues.
Dec 3, 09:36 UTC