Alerts Severity Alignment to Priority Based Severity
Scheduled Maintenance Report for Coralogix
The scheduled maintenance has been completed.
Posted Jul 09, 2024 - 12:59 UTC
In progress
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Posted Jul 09, 2024 - 09:00 UTC
As part of our efforts to provide a coherent solution between all products, we will be aligning the alerts severity across all products with a unified priority scale (values of P1 - P5).
In the first phase we will enforce a UI change only - all alert severities will be converted automatically to the new priorities.
All APIs and Terraform modules should work as usual.

- Coralogix Security Alerts user?
Please note that Coralogix Security severity will be removed from the UI (we will automatically convert the alert severity value to the new priority according to the values in the security severity label).
APIs will not change.
In case you are using any automation based on the alerts - please note that the alert severity might change. In case you are using Terraform to manage Coralogix security alerts - please note you might see some diff between the sate and plan. To prevent this, the alert's Severity in Terraform must match the actual Severity value in Coralogix. Please change the alert’s severity in Terraform according to the mapping presented below.

Severity --> Security Severity --> Priority
Critical --> Critical --> P1
Error --> High --> P2
Warning --> Medium --> P3
Low --> Low --> P4
Info --> Info --> P5

- How will it affect me?
UI will show a different severity for the alerts with values from P1 to P5 with P1 being the highest and P5 the lowest.
Creation of an alert from the UI will be possible only with the Priority values.
Severities of Security Alerts might change according to the values of the security severity label.
Posted Jul 07, 2024 - 13:49 UTC
This scheduled maintenance affected: Alerting and Metric alerts.