We are currently in the middle of an Elasticsearch to OpenSearch migration. As part of the migration, some alerts are going to be triggered (in particular, unassigned shards and settings checks). Those create noise to for the on-call SREs, making their lives more complicated than they should be. We should make sure those alerts are routed to Data Platform SRE (and not the larger SRE teams) and make sure that problematic alerts are downtimed when they are expected.
Problematic alerts
- ElasticSearch unassigned shard check
- OpenSearch unassigned shard check
- ElasticSearch setting check
AC
- Elasticsearch and OpenSearch alerts that are relevant only to DPE SRE are routed to the DPE SRE team, not to the larger SRE group
- During migration, noisy alerts are downtimed appropriately

