-
Story
-
Resolution: Done
-
Normal
-
None
-
None
-
None
-
- JIRALERT{455284cdaed643171dfe040be84c1b4d7bbe45581eeb7201849f997f7b8c81b1afd6ef9c29e52ea521ab3e35fc81da54a4e57b587994376c3cf6451149a31116}
- alertname="deployment_validation_operator_unset_memory_requirements"
- app="backstage"
- cluster="appsrep09ue1"
- hcm-eng-prod
- job="deployment-validation-operator-metrics"
- service="deployment-validation-operator"
-
False
-
-
False
-
None
-
-
Alert[0]: deployment_validation_operator_unset_memory_requirements Validation error for backstage: Indicates when containers do not have memory requests and limits set.
Annotations:
- dashboard = https://grafana.app-sre.devshift.net/d/dashdotdb/dash-db?orgId=1&var-datasource=dashdotdb-rds&var-cluster=appsrep09ue1&var-namespace=backstage-prod
- html_url = https://gitlab.cee.redhat.com/service/app-interface/blob/master/resources/services/deployment-validation-operator/prometheusrules-unset_memory_requirements.yaml.j2
- runbook = Set memory requests and limits for your container based on its requirements. Refer to https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/#requests-and-limits for details.
Labels:
- alertname = deployment_validation_operator_unset_memory_requirements
- app = backstage
- check_description = Indicates when containers do not have memory requests and limits set.
- check_remediation = Set memory requests and limits for your container based on its requirements. Refer to https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/#requests-and-limits for details.
- cluster = appsrep09ue1
- endpoint = http-metrics
- environment = production
- exported_namespace = backstage-prod
- instance = 10.131.2.24:8383
- jiralert = OSDEV
- job = deployment-validation-operator-metrics
- kind = Deployment
- name = matomo
- namespace = openshift-deployment-validation-operator
- namespace_uid = f4a1b80f-dbbf-4f93-9fcf-ff3db4171449
- pod = deployment-validation-operator-56c7d5847b-dlt84
- prometheus = openshift-customer-monitoring/app-sre
- service = deployment-validation-operator
- severity = medium
- uid = 7ad77d73-c5ca-4a7a-8eb1-a983adeb9f84
Source: Prometheus
Alert[1]: deployment_validation_operator_unset_memory_requirements Validation error for backstage: Indicates when containers do not have memory requests and limits set.
Annotations:
- dashboard = https://grafana.app-sre.devshift.net/d/dashdotdb/dash-db?orgId=1&var-datasource=dashdotdb-rds&var-cluster=appsrep09ue1&var-namespace=backstage-prod
- html_url = https://gitlab.cee.redhat.com/service/app-interface/blob/master/resources/services/deployment-validation-operator/prometheusrules-unset_memory_requirements.yaml.j2
- runbook = Set memory requests and limits for your container based on its requirements. Refer to https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/#requests-and-limits for details.
Labels:
- alertname = deployment_validation_operator_unset_memory_requirements
- app = backstage
- check_description = Indicates when containers do not have memory requests and limits set.
- check_remediation = Set memory requests and limits for your container based on its requirements. Refer to https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/#requests-and-limits for details.
- cluster = appsrep09ue1
- endpoint = http-metrics
- environment = production
- exported_namespace = backstage-prod
- instance = 10.131.2.24:8383
- jiralert = OSDEV
- job = deployment-validation-operator-metrics
- kind = Deployment
- name = tangerine-proxy
- namespace = openshift-deployment-validation-operator
- namespace_uid = f4a1b80f-dbbf-4f93-9fcf-ff3db4171449
- pod = deployment-validation-operator-56c7d5847b-dlt84
- prometheus = openshift-customer-monitoring/app-sre
- service = deployment-validation-operator
- severity = medium
- uid = 780a2930-c9fc-4c99-884e-8d0dcd651ecc
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.