5.1.21 ocseppNfStatusUnavailable

Table 5-21 ocseppNfStatusUnavailable

Field Description
Trigger Condition Triggered when all the SEPP services are unavailable, either because the SEPP is getting deployed or purged.
Severity Critical
Alert Details Provided

Summary

namespace: {{$labels.namespace}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }} : All OCSEPP services are unavailable.'

Expression:
absent(up{app_kubernetes_io_part_of="ocsepp",namespace="sepp-namespace"}) or sum(up{app_kubernetes_io_part_of="ocsepp", namespace="sepp-namespace"}) == 0
OID 1.3.6.1.4.1.323.5.3.46.1.2.4089
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 automatically when the SEPP services start becoming available.

Steps:

  1. Check for service specific alerts which may be causing the issues with service exposure.
  2. Run the following command to check if the pod’s status is in “Running” state:
    kubectl –n <namespace> get pod

    If it is not in running state, capture the pod logs and events.

  3. Run the following command to fetch the events as follows:
    kubectl get events --sort-by=.metadata.creationTimestamp -n <namespace>
  4. Refer to the application logs on Kibana and check for database related failures such as connectivity, invalid secrets, and so on. The logs can be filtered based on the services.
  5. Run the following command to check Helm status and make sure there are no errors:
    helm status <helm release name of the desired NF> -n <namespace>
    If it is not in “STATUS: DEPLOYED”, then again capture logs and events.
  6. If the issue persists, capture all the outputs from the above steps and contact My Oracle Support.