From ff07f107599ad70fd644246c18944d755a1c40f2 Mon Sep 17 00:00:00 2001 From: Jamil Date: Fri, 7 Feb 2025 07:12:39 -0800 Subject: [PATCH] chore(portal): Remove GCP alerting for application errors (#8040) As discussed with @bmanifold, we're moving forward with the following monitoring strategy: For infra alerts, stick with GCP. For application-level alerts, use Sentry. Since we already have Sentry configured and working on staging, this PR removes the "Errors in logs" alert since we will be receiving this in Sentry going forward. --- terraform/modules/google-cloud/ops/main.tf | 33 ---------------------- 1 file changed, 33 deletions(-) diff --git a/terraform/modules/google-cloud/ops/main.tf b/terraform/modules/google-cloud/ops/main.tf index 5055334d0..9d34aa47c 100644 --- a/terraform/modules/google-cloud/ops/main.tf +++ b/terraform/modules/google-cloud/ops/main.tf @@ -302,39 +302,6 @@ resource "google_monitoring_alert_policy" "sql_disk_utiliziation_policy" { } } -resource "google_monitoring_alert_policy" "errors" { - project = var.project_id - - display_name = "Errors in logs" - combiner = "OR" - - notification_channels = local.notification_channels - - conditions { - display_name = "Log match condition" - - condition_matched_log { - filter = <<-EOT - resource.type="gce_instance" - (severity>=ERROR OR "Kernel pid terminated" OR "Crash dump is being written") - -protoPayload.@type="type.googleapis.com/google.cloud.audit.AuditLog" - -logName:"/logs/GCEGuestAgent" - -logName:"/logs/OSConfigAgent" - -logName:"/logs/ops-agent-fluent-bit" - -"OpentelemetryFinch" - EOT - } - } - - alert_strategy { - auto_close = "28800s" - - notification_rate_limit { - period = "3600s" - } - } -} - resource "google_monitoring_alert_policy" "production_db_access_policy" { project = var.project_id