5.1.3 ocseppPodsRestart

Table 5-3 ocseppPodsRestart

Field Description
Trigger Condition Triggered when a pod belonging to any of the SEPP services in a namespace has been restarted.
Severity Major
Alert Details Provided

Summary

namespace: {{$labels.namespace}}, kubernetes_pod_name: {{$labels.pod}}, Container: {{$labels.container}} ,timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }} : A Pod has restarted
Expression:
increase(kube_pod_container_status_restarts_total{namespace="sepp-namespace"}[2m]) > 0
OID 1.3.6.1.4.1.323.5.3.46.1.2.4071
Metric Name

kube_pod_container_status_restarts_total

Note: This is a Kubernetes metric. If this metric is not available, use the similar metric as exposed by the monitoring system.
Resolution

The alert is cleared automatically if the specific pod is up.

Steps:

  1. Refer to the application logs on Kibana and filter based on the pod name. Check for database related failures such as connectivity, Kubernetes secrets, and so on.
  2. Run the following command to check orchestration logs for liveness or readiness probe failures:
    kubectl get po -n <namespace>

    Note the full name of the pod that is not running, and use it in the following command:

    kubectl describe pod <desired full pod name> -n <namespace>
  3. Check the database status. For more information, see Oracle Communications Cloud Native Core, cnDBTier User Guide.
  4. If the issue persists, capture all the outputs from the above steps and contact My Oracle Support.