Remove some outdated alerts

Author: PhilippMatthes

helm/library/cortex-alerts/templates/alerts.yaml

@@ -46,62 +46,6 @@ spec:
           Nova will continue to place new VMs, but the placement will be less desirable.
           Thus, no immediate action is needed.
 
-    - alert: CortexSyncNotSuccessful
-      expr: cortex_sync_request_processed_total{component=~"{{ $componentPrefix }}-.*", namespace="{{ $namespaceSelector }}" } - cortex_sync_request_duration_seconds_count{component=~"{{ $componentPrefix }}-.*", namespace="{{ $namespaceSelector }}" } > 0
-      for: 5m
-      labels:
-        context: syncstatus
-        dashboard: cortex/cortex
-        service: cortex
-        severity: warning
-        support_group: workload-management
-      annotations:
-        summary: "`{{`{{$labels.component}}`}}` Sync not successful"
-        description: >
-          `{{`{{$labels.component}}`}}` experienced an issue syncing data from a datasource. This may
-          happen when the datasource (OpenStack, Prometheus, etc.) is down or
-          the sync module is misconfigured. No immediate action is needed, since
-          the sync module will retry the sync operation and the currently synced
-          data will be kept. However, when this problem persists for a longer
-          time the service will have a less recent view of the datacenter.
-
-    - alert: CortexSyncObjectsDroppedToZero
-      expr: cortex_sync_objects{component=~"{{ $componentPrefix }}-.*", datasource!="openstack_migrations", namespace="{{ $namespaceSelector }}" } == 0
-      for: 60m
-      labels:
-        context: syncobjects
-        dashboard: cortex/cortex
-        service: cortex
-        severity: warning
-        support_group: workload-management
-      annotations:
-        summary: "`{{`{{$labels.component}}`}}` is not syncing any new data from `{{`{{$labels.datasource}}`}}`"
-        description: >
-          `{{`{{$labels.component}}`}}` is not syncing any objects from a datasource. This may happen
-          when the datasource (OpenStack, Prometheus, etc.) is down or the sync
-          module is misconfigured. No immediate action is needed, since the sync
-          module will retry the sync operation and the currently synced data will
-          be kept. However, when this problem persists for a longer time the
-          service will have a less recent view of the datacenter.
-
-    - alert: CortexSyncObjectsTooHigh
-      expr: cortex_sync_objects{component=~"{{ $componentPrefix }}-.*", namespace="{{ $namespaceSelector }}" } > 10000000
-      for: 5m
-      labels:
-        context: syncobjects
-        dashboard: cortex/cortex
-        service: cortex
-        severity: warning
-        support_group: workload-management
-      annotations:
-        summary: "`{{`{{$labels.component}}`}}` is syncing unexpectedly many objects from `{{`{{$labels.datasource}}`}}`"
-        description: >
-          `{{`{{$labels.component}}`}}` is syncing more than 1 million objects from a datasource. This
-          may happen when the datasource (OpenStack, Prometheus, etc.) returns
-          unexpectedly many objects, or when the database cannot drop old objects.
-          No immediate action is needed, but should this condition persist for a
-          longer time, the database may fill up and crash.
-
     - alert: CortexHighMemoryUsage
       expr: process_resident_memory_bytes{component=~"{{ $componentPrefix }}-.*", namespace="{{ $namespaceSelector }}" } > 6000 * 1024 * 1024
       for: 5m