The operator does not support all features available for prometheus alerts.

[ankitdh7]

Problem
The operator allows configuring alerts from PrometheusRule CRDs as metric alerts, but there are some features available in the Coralogix UI that cannot be managed through the operator. For instance, options like "Set as Security Alert," various notification settings, scheduling etc are not supported via the operator.

Actual
The operator currently manages only a limited set of alert functionalities provided by the Coralogix platform.

Expected
The operator should support configuring all aspects of alerts that are available in the Coralogix UI. Any limitations or unsupported features should be clearly documented to avoid confusion.

[assafad1]

@ankitdh7 Hi, the Alert CRD supports all the options you mentioned, but not all are supported from the PrometheusRule, as its alert configuration is more basic. For instance, Set as Security Alert can be achieved by adding a label alert_type: security to the alert in the PrometheusRule, since it's only a label, but other options are available only from the Alert CRD itself. We don't believe that the operator should support all the Alert properties from the PrometheusRule as it will be inconvenient to use labels and annotations for that. Coralogix Alerts are more complex and PrometheusRule is mainly responsible to ease the integration process. However, I do think we lack documentation regarding this transition from PrometheusRule to Alert CRDs (#195) , and we will add it.