5.3.11 OcnrfNFStatusTransitionToSuspended

Table 5-56 OcnrfNFStatusTransitionToSuspended

Field Details
Description 'NF with NF profile fqdn {{$labels.NfProfileFqdn}} NF instance id {{$labels.NfInstanceId}} NF type {{$labels.NfType}} is SUSPENDED, previous status was {{$labels.PreviousStatus}}'
Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}},nrflevel:{{$labels.NrfLevel}},podname: {{$labels.kubernetes_pod_name}},NfInstanceId: {{$labels.NfInstanceId}},NfProfileFqdn: {{$labels.NfProfileFqdn}},NfType: {{$labels.NfType}},PreviousStatus: {{$labels.PreviousStatus}},NewStatus: {{$labels.NewStatus}},timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }} NF is SUSPENDED.'
Severity Major
Condition NF Instance's status transitions to SUSPENDED.

Note: When multiple alerts are present for a given NF, the latest alert is always considered. The timestamp can also be seen in the "Active Since" field of the alert in Prometheus.

OID 1.3.6.1.4.1.323.5.3.36.1.2.7048
Metric Used ocnrf_nfInstance_status_change_total
Recommended Actions The alert is cleared automatically after a window of 5 minutes.
Steps:
  1. Check logs in NRF registration pod for failing patch requests or check Jaeger traces to see traces for incoming requests.
  2. Check Ingress Gateway logs to see if the requests are coming.
  3. Check if the NRF pods are UP.
  4. Check for the Ingress Gateway metrics in Prometheus for PATCH requests or responses in this time frame. Confirm if the responses have any non-2xx error codes.
  5. Depending on the failure reason, take the resolution steps.
  6. In case the issue persists, capture all the outputs for the above steps and contact My Oracle Support.

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

Available in OCI Yes