5.1.5 ocseppCn32cServiceDown

Table 5-5 ocseppCn32cServiceDown

Field Description
Trigger Condition Triggered when cn32c-svc service is unavailable.
Severity Critical
Alert Details Provided

Summary

'namespace: {{$labels.namespace}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }} : OCSEPP {{$labels.app_kubernetes_io_name}} service down'

Expression:
absent(up{app_kubernetes_io_name="cn32c-svc",namespace="sepp-namespace"}) or sum by(namespace, app_kubernetes_io_name) (up{app_kubernetes_io_name="cn32c-svc",namespace="sepp-namespace"}) == 0
OID 1.3.6.1.4.1.323.5.3.46.1.2.4073
Metric Name

up

Note: This is a Prometheus metric used for instance availability monitoring. If this metric is not available, use the similar metric as exposed by the monitoring system.
Resolution The alert is cleared when the cn32c-svc services are available.

Steps:

  1. Run the following command to check the orchestration log of cn32c-svc and check 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 <specific desired full pod name> -n <namespace>
  2. Refer to the application logs on Kibana and filter based on above service name. Check for ERROR and WARNING logs related to this service.
  3. Check the database status. For more information, see Oracle Communications Cloud Native Core, cnDBTier User Guide.
  4. Depending on the failure reason, take the resolution steps.
  5. If the issue persists, capture all the outputs from the above steps and contact My Oracle Support.