-
Task
-
Resolution: Done
-
Normal
-
None
-
None
-
None
-
- JIRALERT{ddafb6a104deffb10b3edd677a00edbb7a3c314180f084e8688a4843b931cdfff36e960a153d9495e09ed05bd1d9821a762b0418a9c35de2d75930e59c621886}
- alertname="deployment_validation_operator_minimum_three_replicas"
- app="rhsm-api-proxy"
- cluster="crcp01ue1"
- job="deployment-validation-operator-metrics"
- service="deployment-validation-operator"
-
False
-
-
False
Alert: deployment_validation_operator_minimum_three_replicas Validation error for rhsm-api-proxy: Indicates when a deployment uses less than three replicas
Annotations:
- dashboard = https://grafana.app-sre.devshift.net/d/dashdotdb/dash-db?orgId=1&var-datasource=dashdotdb-rds&var-cluster=crcp01ue1&var-namespace=rhsm-api-proxy-prod
- html_url = https://gitlab.cee.redhat.com/service/app-interface/blob/master/resources/services/deployment-validation-operator/prometheusrules-minimum_three_replicas.yaml.j2
- runbook = Increase be number of replicas in the deployment to at least three to increase the fault tolerancy of the deployment.
Labels:
- alertname = deployment_validation_operator_minimum_three_replicas
- app = rhsm-api-proxy
- check_description = Indicates when a deployment uses less than three replicas
- check_remediation = Increase be number of replicas in the deployment to at least three to increase the fault tolerancy of the deployment.
- cluster = crcp01ue1
- endpoint = http-metrics
- environment = production
- exported_namespace = rhsm-api-proxy-prod
- instance = 10.129.10.12:8383
- jiralert = ENT
- job = deployment-validation-operator-metrics
- kind = Deployment
- name = rhsm-api-proxy-service
- namespace = deployment-validation-operator
- pod = deployment-validation-operator-6cbcbbbfd5-x9zhc
- prometheus = openshift-customer-monitoring/app-sre
- service = deployment-validation-operator
- severity = medium
Source: Prometheus
Note: This issue was generated automatically by the AppSRE team. Moving this issue to a different project will result in the ticket being recreated in the current project. If you believe that this issue was created in the incorrect project, please reach out to AppSRE.