-
Task
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
None
-
- JIRALERT{56b97a11b0c6e66efbcc10f3113d5f58137fdf8b4e43fe89818f7144ea56bd5d9e0819e93153fca5fe3301367f7b17468964e6d8a9ea2d01f350ed7e6c7edd7e}
- alertname="deployment_validation_operator_no_liveness_probe"
- app="tower-analytics"
- cluster="appsres03ue1"
- job="deployment-validation-operator-metrics"
- service="deployment-validation-operator"
-
False
-
-
False
-
Sprint 34 - Platform Services
Alert: deployment_validation_operator_no_liveness_probe Validation error for tower-analytics: 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=appsres03ue1&var-namespace=tower-analytics-stage-tests
- 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 = tower-analytics
- 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 = appsres03ue1
- endpoint = http-metrics
- environment = staging
- exported_namespace = tower-analytics-stage-tests
- instance = 10.129.4.30:8383
- jiralert = AA
- job = deployment-validation-operator-metrics
- kind = Pod
- name = acceptance-cypress-6ea31e6-c5a8d0d-kbbz2
- namespace = deployment-validation-operator
- pod = deployment-validation-operator-6cbcbbbfd5-tcs9z
- 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.