We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
resource "coralogix_alert" "count_get_response_times_warning" { name = "${local.alert_display_name} [Number of GET with response times P90 >= 500ms]" enabled = var.enable_alerts severity = "Warning" meta_labels = { application = var.aws_account_name subsystem = var.ecs_service_name } standard { search_query = ".......omitted..... AND http_request.duration_ms: [500 TO *} ${local.get_http_method_condition_q1}" applications = [var.aws_account_name] subsystems = [var.ecs_service_name] severities = [ "Info", "Error" ] condition { more_than = true threshold = var.cx_get_slow_request_threshold time_window = var.cx_get_slow_request_time_window } } }
Error: internal error in Coralogix backend. │ error - rpc error: code = Internal desc = statusCode: 400, response: {"success":false,"status":400,"message":"alert definition, notificationGroups is invalid , SequelizeValidationError: Must have at least 1 notificationGroups item"} │ url - com.coralogix.alerts.v2.AlertService/CreateAlert
notification_group should be either documented as required or allowed to be optional in CX backend
notification_group
notification_group must be specified otherwise TF plan fails
Coralogix TF provider v1.14.1 TF v1.8.2
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Affected Resource(s)
Terraform Configuration Files
Debug Output
Expected Behavior
notification_group
should be either documented as required or allowed to be optional in CX backendActual Behavior
notification_group
must be specified otherwise TF plan failsImportant Factoids
Coralogix TF provider v1.14.1
TF v1.8.2
Community Note
The text was updated successfully, but these errors were encountered: