-
Task
-
Resolution: Done
-
Normal
-
None
-
None
-
None
-
- JIRALERT{36a28eb31411db04d8176f9efbc69feb7aa3bc6446f163fb2a8fcec6f8322cbfd9e645458a1bc5f71f89ec6fb0a88b1482e70a534df8670887d31a65b8b548e1}
- alertname="deployment_validation_operator_unset_cpu_requirements"
- app="tower-analytics"
- cluster="crcs02ue1"
- job="deployment-validation-operator-metrics"
- service="deployment-validation-operator"
-
False
-
-
False
-
-
Alert[0]: deployment_validation_operator_unset_cpu_requirements Validation error for tower-analytics: Indicates when containers do not have CPU requests and limits set.
Annotations:
- dashboard = https://grafana.app-sre.devshift.net/d/dashdotdb/dash-db?orgId=1&var-datasource=dashdotdb-rds&var-cluster=crcs02ue1&var-namespace=tower-analytics-stage
- html_url = https://gitlab.cee.redhat.com/service/app-interface/blob/master/resources/services/deployment-validation-operator/prometheusrules-unset_cpu_requirements.yaml.j2
- runbook = Set CPU 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_cpu_requirements
- app = tower-analytics
- check_description = Indicates when containers do not have CPU requests and limits set.
- check_remediation = Set CPU 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 = crcs02ue1
- endpoint = http-metrics
- environment = staging
- exported_namespace = tower-analytics-stage
- instance = 10.130.8.25:8383
- jiralert = AA
- job = deployment-validation-operator-metrics
- kind = Job
- name = 2021-04-21-1-explain-a-export-job-events-fk-alternative-stage
- namespace = openshift-deployment-validation-operator
- namespace_uid = b9dc7c1a-7004-48ef-ab82-6df6a803c22a
- pod = deployment-validation-operator-6fdbdf5597-zr2qv
- prometheus = openshift-customer-monitoring/app-sre
- service = deployment-validation-operator
- severity = medium
- uid = 6a65f224-3759-4940-ad0f-4556083df620
Source: Prometheus
Alert[1]: deployment_validation_operator_unset_cpu_requirements Validation error for tower-analytics: Indicates when containers do not have CPU requests and limits set.
Annotations:
- dashboard = https://grafana.app-sre.devshift.net/d/dashdotdb/dash-db?orgId=1&var-datasource=dashdotdb-rds&var-cluster=crcs02ue1&var-namespace=tower-analytics-stage
- html_url = https://gitlab.cee.redhat.com/service/app-interface/blob/master/resources/services/deployment-validation-operator/prometheusrules-unset_cpu_requirements.yaml.j2
- runbook = Set CPU 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_cpu_requirements
- app = tower-analytics
- check_description = Indicates when containers do not have CPU requests and limits set.
- check_remediation = Set CPU 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 = crcs02ue1
- endpoint = http-metrics
- environment = staging
- exported_namespace = tower-analytics-stage
- instance = 10.130.8.25:8383
- jiralert = AA
- job = deployment-validation-operator-metrics
- kind = Job
- name = 2021-04-21-1-explain-a-export-job-events-fk-stage
- namespace = openshift-deployment-validation-operator
- namespace_uid = b9dc7c1a-7004-48ef-ab82-6df6a803c22a
- pod = deployment-validation-operator-6fdbdf5597-zr2qv
- prometheus = openshift-customer-monitoring/app-sre
- service = deployment-validation-operator
- severity = medium
- uid = d82d2e47-8ec2-4fe8-968b-3c85df605a88
Source: Prometheus
Alert[2]: deployment_validation_operator_unset_cpu_requirements Validation error for tower-analytics: Indicates when containers do not have CPU requests and limits set.
Annotations:
- dashboard = https://grafana.app-sre.devshift.net/d/dashdotdb/dash-db?orgId=1&var-datasource=dashdotdb-rds&var-cluster=crcs02ue1&var-namespace=tower-analytics-stage
- html_url = https://gitlab.cee.redhat.com/service/app-interface/blob/master/resources/services/deployment-validation-operator/prometheusrules-unset_cpu_requirements.yaml.j2
- runbook = Set CPU 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_cpu_requirements
- app = tower-analytics
- check_description = Indicates when containers do not have CPU requests and limits set.
- check_remediation = Set CPU 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 = crcs02ue1
- endpoint = http-metrics
- environment = staging
- exported_namespace = tower-analytics-stage
- instance = 10.130.8.25:8383
- jiralert = AA
- job = deployment-validation-operator-metrics
- kind = Job
- name = 2021-04-21-1-explain-export-job-events-fk-alternative-stage
- namespace = openshift-deployment-validation-operator
- namespace_uid = b9dc7c1a-7004-48ef-ab82-6df6a803c22a
- pod = deployment-validation-operator-6fdbdf5597-zr2qv
- prometheus = openshift-customer-monitoring/app-sre
- service = deployment-validation-operator
- severity = medium
- uid = 30e94eb7-a71b-46be-8db7-cc71bf64578c
Source: Prometheus
Alert[3]: deployment_validation_operator_unset_cpu_requirements Validation error for tower-analytics: Indicates when containers do not have CPU requests and limits set.
Annotations:
- dashboard = https://grafana.app-sre.devshift.net/d/dashdotdb/dash-db?orgId=1&var-datasource=dashdotdb-rds&var-cluster=crcs02ue1&var-namespace=tower-analytics-stage
- html_url = https://gitlab.cee.redhat.com/service/app-interface/blob/master/resources/services/deployment-validation-operator/prometheusrules-unset_cpu_requirements.yaml.j2
- runbook = Set CPU 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_cpu_requirements
- app = tower-analytics
- check_description = Indicates when containers do not have CPU requests and limits set.
- check_remediation = Set CPU 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 = crcs02ue1
- endpoint = http-metrics
- environment = staging
- exported_namespace = tower-analytics-stage
- instance = 10.130.8.25:8383
- jiralert = AA
- job = deployment-validation-operator-metrics
- kind = Job
- name = 2021-04-21-1-explain-export-job-events-fk-stage
- namespace = openshift-deployment-validation-operator
- namespace_uid = b9dc7c1a-7004-48ef-ab82-6df6a803c22a
- pod = deployment-validation-operator-6fdbdf5597-zr2qv
- prometheus = openshift-customer-monitoring/app-sre
- service = deployment-validation-operator
- severity = medium
- uid = 397ba089-942d-4909-af15-3455b58d64e4
Source: Prometheus
Alert[4]: deployment_validation_operator_unset_cpu_requirements Validation error for tower-analytics: Indicates when containers do not have CPU requests and limits set.
Annotations:
- dashboard = https://grafana.app-sre.devshift.net/d/dashdotdb/dash-db?orgId=1&var-datasource=dashdotdb-rds&var-cluster=crcs02ue1&var-namespace=tower-analytics-stage
- html_url = https://gitlab.cee.redhat.com/service/app-interface/blob/master/resources/services/deployment-validation-operator/prometheusrules-unset_cpu_requirements.yaml.j2
- runbook = Set CPU 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_cpu_requirements
- app = tower-analytics
- check_description = Indicates when containers do not have CPU requests and limits set.
- check_remediation = Set CPU 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 = crcs02ue1
- endpoint = http-metrics
- environment = staging
- exported_namespace = tower-analytics-stage
- instance = 10.130.8.25:8383
- jiralert = AA
- job = deployment-validation-operator-metrics
- kind = Job
- name = 2021-04-21-explain-a-export-job-events-fk-alternative-stage
- namespace = openshift-deployment-validation-operator
- namespace_uid = b9dc7c1a-7004-48ef-ab82-6df6a803c22a
- pod = deployment-validation-operator-6fdbdf5597-zr2qv
- prometheus = openshift-customer-monitoring/app-sre
- service = deployment-validation-operator
- severity = medium
- uid = f6a06ab5-1d41-4925-81ca-2180bd51536b
Source: Prometheus
Alert[5]: deployment_validation_operator_unset_cpu_requirements Validation error for tower-analytics: Indicates when containers do not have CPU requests and limits set.
Annotations:
- dashboard = https://grafana.app-sre.devshift.net/d/dashdotdb/dash-db?orgId=1&var-datasource=dashdotdb-rds&var-cluster=crcs02ue1&var-namespace=tower-analytics-stage
- html_url = https://gitlab.cee.redhat.com/service/app-interface/blob/master/resources/services/deployment-validation-operator/prometheusrules-unset_cpu_requirements.yaml.j2
- runbook = Set CPU 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_cpu_requirements
- app = tower-analytics
- check_description = Indicates when containers do not have CPU requests and limits set.
- check_remediation = Set CPU 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 = crcs02ue1
- endpoint = http-metrics
- environment = staging
- exported_namespace = tower-analytics-stage
- instance = 10.130.8.25:8383
- jiralert = AA
- job = deployment-validation-operator-metrics
- kind = Job
- name = 2021-04-21-explain-a-export-job-events-fk-stage
- namespace = openshift-deployment-validation-operator
- namespace_uid = b9dc7c1a-7004-48ef-ab82-6df6a803c22a
- pod = deployment-validation-operator-6fdbdf5597-zr2qv
- prometheus = openshift-customer-monitoring/app-sre
- service = deployment-validation-operator
- severity = medium
- uid = f1f4093a-66a0-452f-8d53-fd4c7d054f76
Source: Prometheus
Alert[6]: deployment_validation_operator_unset_cpu_requirements Validation error for tower-analytics: Indicates when containers do not have CPU requests and limits set.
Annotations:
- dashboard = https://grafana.app-sre.devshift.net/d/dashdotdb/dash-db?orgId=1&var-datasource=dashdotdb-rds&var-cluster=crcs02ue1&var-namespace=tower-analytics-stage
- html_url = https://gitlab.cee.redhat.com/service/app-interface/blob/master/resources/services/deployment-validation-operator/prometheusrules-unset_cpu_requirements.yaml.j2
- runbook = Set CPU 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_cpu_requirements
- app = tower-analytics
- check_description = Indicates when containers do not have CPU requests and limits set.
- check_remediation = Set CPU 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 = crcs02ue1
- endpoint = http-metrics
- environment = staging
- exported_namespace = tower-analytics-stage
- instance = 10.130.8.25:8383
- jiralert = AA
- job = deployment-validation-operator-metrics
- kind = Job
- name = 2021-04-21-explain-export-job-events-fk-alternative-stage
- namespace = openshift-deployment-validation-operator
- namespace_uid = b9dc7c1a-7004-48ef-ab82-6df6a803c22a
- pod = deployment-validation-operator-6fdbdf5597-zr2qv
- prometheus = openshift-customer-monitoring/app-sre
- service = deployment-validation-operator
- severity = medium
- uid = 7451abb6-b70a-45fd-9403-2576d4cc16f1
Source: Prometheus
Alert[7]: deployment_validation_operator_unset_cpu_requirements Validation error for tower-analytics: Indicates when containers do not have CPU requests and limits set.
Annotations:
- dashboard = https://grafana.app-sre.devshift.net/d/dashdotdb/dash-db?orgId=1&var-datasource=dashdotdb-rds&var-cluster=crcs02ue1&var-namespace=tower-analytics-stage
- html_url = https://gitlab.cee.redhat.com/service/app-interface/blob/master/resources/services/deployment-validation-operator/prometheusrules-unset_cpu_requirements.yaml.j2
- runbook = Set CPU 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_cpu_requirements
- app = tower-analytics
- check_description = Indicates when containers do not have CPU requests and limits set.
- check_remediation = Set CPU 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 = crcs02ue1
- endpoint = http-metrics
- environment = staging
- exported_namespace = tower-analytics-stage
- instance = 10.130.8.25:8383
- jiralert = AA
- job = deployment-validation-operator-metrics
- kind = Job
- name = 2021-04-21-explain-export-job-events-fk-stage
- namespace = openshift-deployment-validation-operator
- namespace_uid = b9dc7c1a-7004-48ef-ab82-6df6a803c22a
- pod = deployment-validation-operator-6fdbdf5597-zr2qv
- prometheus = openshift-customer-monitoring/app-sre
- service = deployment-validation-operator
- severity = medium
- uid = 79035483-9bdb-4280-bfdb-5f913f0a14cc
Source: Prometheus
Alert[8]: deployment_validation_operator_unset_cpu_requirements Validation error for tower-analytics: Indicates when containers do not have CPU requests and limits set.
Annotations:
- dashboard = https://grafana.app-sre.devshift.net/d/dashdotdb/dash-db?orgId=1&var-datasource=dashdotdb-rds&var-cluster=crcs02ue1&var-namespace=tower-analytics-stage
- html_url = https://gitlab.cee.redhat.com/service/app-interface/blob/master/resources/services/deployment-validation-operator/prometheusrules-unset_cpu_requirements.yaml.j2
- runbook = Set CPU 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_cpu_requirements
- app = tower-analytics
- check_description = Indicates when containers do not have CPU requests and limits set.
- check_remediation = Set CPU 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 = crcs02ue1
- endpoint = http-metrics
- environment = staging
- exported_namespace = tower-analytics-stage
- instance = 10.130.8.25:8383
- jiralert = AA
- job = deployment-validation-operator-metrics
- kind = Job
- name = acceptance-gating-a43ba1c-3c1ad42
- namespace = openshift-deployment-validation-operator
- namespace_uid = b9dc7c1a-7004-48ef-ab82-6df6a803c22a
- pod = deployment-validation-operator-6fdbdf5597-zr2qv
- prometheus = openshift-customer-monitoring/app-sre
- service = deployment-validation-operator
- severity = medium
- uid = 8b8b68aa-285c-45a4-892f-6e2f0dfd7405
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.