5.4.13.4 OcnrfCacheDataServiceDown

Table 5-109 OcnrfCacheDataServiceDown

Field Details
Description 'OCNRF NrfCacheData service {{$labels.app_kubernetes_io_name}} is down'
Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }} : Cache Data Service is down'
Severity Critical
Condition Cache Data Service is unavailable.
OID 1.3.6.1.4.1.323.5.3.36.1.2.7101
Metric Used up
Recommended Actions

The alert is cleared when the Cache Data Service (CDS) is available.

Steps:
  1. To check the orchestration logs of the CDS and check for liveness or readiness probe failures, do the following:
    1. Run the following command to check the pod status:
      $ kubectl get po -n <namespace>
    2. Run the following command to analyze the error condition of the pod that is not in the running state:
      $ kubectl describe pod <pod name not in Running state> -n <namespace>

      Where <pod name not in Running state> indicates the pod that is not in the Running state.

  2. Refer to the application logs on Kibana and filter based on service names. Check for ERROR WARNING logs.
  3. Check the DB status. For more information on how to check the DB status, see Oracle Communications Cloud Native Core, cnDBTier User Guide. Depending on the failure reason, take the resolution steps.
  4. In case the issue persists, capture all the outputs for the above steps and contact My Oracle Support.

Note: Use the CNC NF Data Collector tool for capturing logs. For more information on how to collect logs using the Data Collector tool, see Oracle Communications Cloud Native Core, Network Function Data Collector User Guide.

Available in OCI No