-
Task
-
Resolution: Done
-
Major
-
None
-
None
-
None
-
- JIRALERT{0cddaec258d050b7a37282d038d63716d9e70cd28b80243447bd72eca1e9c100163960a8ec07a0b1265e06b52bd6d243c383999c76767e97a271ae9ba8b2621f}
- alertname="deployment_validation_operator_no_liveness_probe"
- app="rhose"
- cluster="app-sre-stage-01"
- job="deployment-validation-operator-metrics"
- service="deployment-validation-operator"
-
False
-
None
-
False
Alert: deployment_validation_operator_no_liveness_probe Validation error for rhose: Indicates when containers fail to specify a liveness probe.
Annotations:
- dashboard = https://grafana.app-sre.devshift.net/d/dashdotdb/dash-db?orgId=1&var-datasource=dashdotdb-rds&var-cluster=app-sre-stage-01&var-namespace=rhose-stage
- html_url = https://gitlab.cee.redhat.com/service/app-interface/blob/master/resources/services/deployment-validation-operator/prometheusrules-no_liveness_probe.yaml.j2
- runbook = Specify a liveness probe in your container. Refer to https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/ for details.
Labels:
- alertname = deployment_validation_operator_no_liveness_probe
- app = rhose
- check_description = Indicates when containers fail to specify a liveness probe.
- check_remediation = Specify a liveness probe in your container. Refer to https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/ for details.
- cluster = app-sre-stage-01
- endpoint = http-metrics
- environment = staging
- exported_namespace = rhose-stage
- instance = 10.128.34.11:8383
- jiralert = MGDOBR
- job = deployment-validation-operator-metrics
- kind = Deployment
- name = diag-container
- namespace = deployment-validation-operator
- pod = deployment-validation-operator-646d8db489-9cnn5
- 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.