All Systems Operational
Log Collection ? Operational
90 days ago
100.0 % uptime
Today
Log Processing ? Operational
90 days ago
100.0 % uptime
Today
User Interface ? Operational
90 days ago
99.94 % uptime
Today
Alerting ? Operational
90 days ago
100.0 % uptime
Today
Live Tail ? Operational
90 days ago
100.0 % uptime
Today
Archiving ? Operational
90 days ago
100.0 % uptime
Today
ES API ? Operational
90 days ago
100.0 % uptime
Today
Metrics Processing ? Operational
90 days ago
100.0 % uptime
Today
Tracing collection ? Operational
90 days ago
100.0 % uptime
Today
Metric alerts Operational
90 days ago
100.0 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
Scheduled Maintenance
Dear Customers,
We want to keep you informed about important updates and changes to Azure Application Insights.

End of Support for Classic Application Insights
Effective Date: 29th of February 2024
Azure is ending support for Classic Application Insights, impacting how integration performance monitoring is captured. This change is significant for all Azure deployments currently utilizing Classic Application Insights for monitoring logs and performance details.

Impact of the Change
Post the effective date, Azure deployments will no longer receive Application Insights capture, affecting your ability to monitor logs or performance details for your Azure integrations.

Options for Customers
To mitigate the impact of this change, customers are presented with two options:
1. Re-deploy Azure Integrations: Utilize an updated integration that incorporates Workspace-based Application Insights. This approach ensures continued access to monitoring capabilities without interruption
2. Manual Migration: Customers may opt to manually migrate to Workspace-based Application Insights (see instructions here - https://learn.microsoft.com/en-us/azure/azure-monitor/app/convert-classic-resource#migrate-your-resource). While migration is not mandatory, and your integration will continue to run, monitoring capabilities will be unavailable until migration is complete.

Availability of the New Integration
The new integration option is currently accessible via the ARM template direct deployment method (available in our Github repository - https://github.com/coralogix/coralogix-azure-serverless/tree/master). Update to facilitate deployment via the Coralogix UI Integration have been made, TF deployment is underway and will be announced shortly.

Action Required
We encourage all affected customers to consider the provided options and take necessary actions well before the end-of-support date to ensure continuous monitoring of your Azure integrations.

Need Assistance?
Should you have any questions or require assistance with migration, our support team and Technical Account Managers are here to help. Please don’t hesitate to reach out for support or more information.

Posted on Feb 22, 2024 - 16:28 UTC
We’re excited to announce the launch of our latest offering: the Coralogix-AWS-Shipper Lambda.
This new and improved Lambda is set to streamline our services by replacing several existing ones, including:
S3, CloudTrail, CloudWatch Logs, SNS, Athena, VPC Flow, Kafka, MSK, Kinesis, SQS, and ECR, offering a more integrated and efficient solution.
We highly recommend adopting this new Lambda for your upcoming integration projects and upgrading for your existing Lambdas (removing the old one and installing the new one).
The old Lambda will be deprecated on May 1st, 2024, this is particularly timely in light of AWS’s planned deprecation of Node 16 on June 12th, 2024.
For details on deploying via CloudFormation and Terraform, please visit our GitHub page - https://coralogix.com/docs/aws-integration-guide/
We’re here to support you in making this transition smooth and rewarding. For any questions please don’t hesitate to contact your Technical Account Manager or Coralogix chat support.

Posted on Feb 05, 2024 - 05:51 UTC
Dear Customers,

In our continuous effort to streamline data processing and enhance the clarity of metrics within our platform, we are implementing an update to the labeling system for metrics ingested using OTLP (OpenTelemetry Protocol) and Firehose integrations. This update is scheduled to take effect on May 21st 2024.

Labels Being Removed and Their Replacements:

We have identified certain labels that create redundancies in metric data.
To simplify metric analysis and reduce confusion, the following labels will be removed and their functionalities will be fully covered by existing labels:

__meta_applicationname will be removed. Its function duplicates cx_application_name.
__meta_subsystem will be removed. Its function duplicates cx_subsystem_name.
account_id will be removed. Its function duplicates cloud_account_id.
__aws_region will be removed. Its function duplicates cloud_region.

We understand that changes to your data ingestion process may require adjustments on your end. Our support team and TAM are here to assist you with any questions or concerns you may have regarding this update. Please don’t hesitate to reach out to us.

Posted on Feb 20, 2024 - 13:50 UTC
Past Incidents
Feb 24, 2024
Resolved - This incident has been resolved.
Feb 24, 09:41 UTC
Investigating - Customers who store in their data in our Ireland region (team.coralogix.com) experience delay with their metric data.
Our team is working on solving this issue ASAP.
To prevent false-positive notifications, we have disabled metric alerts in this environment.

For any question you can reach out to our team via in-app support.

Feb 24, 07:25 UTC
Resolved - Our team has handled the delay in data ingestion and enabled metric alerts for all customers.
Feb 24, 01:16 UTC
Investigating - Customers who store in their data in our Ireland region (team.coralogix.com) experience delay with their metric data.
Our team is working on solving this issue ASAP.
To prevent false-positive notifications, we have disabled metric alerts in this environment.

For any question you can reach out to our team via in-app support.

Feb 24, 00:54 UTC
Feb 23, 2024
Resolved - Our team has identified an incident that affected companies using the (eu-west-1) - Ireland region (team.coralogix.com).
During this incident, users were not able to login or use Coralogix pages. There was no impact on data and either on alerts.
Our team has identified the root cause and taken corrective actions to ensure this specific issue does not reoccur.

Feb 23, 12:14 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Feb 23, 10:52 UTC
Identified - The issue has been identified and a fix is being implemented.
Feb 23, 10:50 UTC
Investigating - The implemented fix didn't resolve the issue permanently. R&D is investigating it further
Feb 23, 09:09 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Feb 23, 09:03 UTC
Identified - The issue has been identified and a fix has been implemented.
Feb 23, 09:02 UTC
Investigating - Our team is investigating this matter.
No impact on the data itself. Alerts engine and alert notifications are not affected by the issue.
We are on it with top priority and will update once resolved.
Please contact our in-app support for any additional questions.

Feb 23, 08:30 UTC
Feb 22, 2024
Resolved - This incident has been resolved.
Feb 22, 12:44 UTC
Investigating - Currently, Coralogix support is affected by an incident with our in-app chat vendor.
For urgent matters, please contact support@coralogix.com or via shared Slack channels.

https://www.intercomstatus.com/incidents/15h532sk1ytv

Feb 22, 08:59 UTC
Feb 21, 2024
Resolved - Coralogix customers utilizing our US West region (cx498 URL accounts) may encounter intermittent issues with data shipping into their accounts due to an AWS incident affecting the Global region.

The incident occurred on February 21st, commencing at 5:49 PM PST and concluding at 7:07 PM PST, during which a global operational issue was identified within the AWS US West region. Further details regarding the incident can be found here: AWS Health Dashboard.
This disruption impacted a total of 31 AWS services, including vital services such as VPC, AWS LB, and EKS. The repercussions extended to Coralogix clusters, potentially leading to data loss.

While Coralogix demonstrates resilience to Availability Zone (AZ) failures, we do not maintain the capacity to sustain uninterrupted service in the event of a complete region outage, due to our current infrastructure design. Although we prioritize high availability and data integrity through redundant systems and failover mechanisms within a region, a regional outage presents additional challenges.
We apologize for any inconvenience caused by this disruption.

Feb 21, 00:00 UTC
Feb 20, 2024
Completed - The scheduled maintenance has been completed.
Feb 20, 13:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Feb 20, 09:00 UTC
Scheduled - As part of our effort to make our platform stable and secure, we are planning to upgrade our data receiving endpoints. This upgrade is expected to last approximately 4 hours.
The upgrade will take place on AP2 (ap-south-1, .app.coralogixsg.com)
We do not anticipate any impact on our customers during this upgrade.
Our team is available 24/7 via our in-app chat if you have any questions or concerns.

Feb 18, 12:02 UTC
Feb 19, 2024

No incidents reported.

Feb 18, 2024

No incidents reported.

Feb 17, 2024

No incidents reported.

Feb 16, 2024

No incidents reported.

Feb 15, 2024

No incidents reported.

Feb 14, 2024

No incidents reported.

Feb 13, 2024

No incidents reported.

Feb 12, 2024

No incidents reported.

Feb 11, 2024

No incidents reported.

Feb 10, 2024

No incidents reported.