-
Task
-
Resolution: Done
-
Normal
-
None
-
None
-
None
-
- JIRALERT{e23b6629eac069ea425f57cea494d5321c7788dc6cf34d55ed0339ba1427b1edeff799a4ecd9b7bfe8836baefcfe5db2d924a0736810c9dd5caae188f1342f90}
- alertname="deployment_validation_operator_no_liveness_probe"
- app="blackbox-monitor"
- cluster="crcs02ue1"
- job="deployment-validation-operator-metrics"
- service="deployment-validation-operator"
-
False
-
-
False
-
Unset
-
None
Alert: deployment_validation_operator_no_liveness_probe Validation error for blackbox-monitor: 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=crcs02ue1&var-namespace=blackbox-monitor-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 = blackbox-monitor
- 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 = crcs02ue1
- endpoint = http-metrics
- environment = staging
- exported_namespace = blackbox-monitor-stage
- instance = 10.130.2.37:8383
- jiralert = RHCLOUD
- job = deployment-validation-operator-metrics
- kind = Pod
- name = blackbox-monitor-debug
- namespace = deployment-validation-operator
- pod = deployment-validation-operator-6cbcbbbfd5-xx4hr
- 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.