5.3.13 OcnrfNFStatusTransitionToUndiscoverable

Table 5-58 OcnrfNFStatusTransitionToUndiscoverable

Field Details
Description 'NF with NF profile fqdn {{$labels.NfProfileFqdn}} NF instance id {{$labels.NfInstanceId}} NF type {{$labels.NfType}} is UNDISCOVERABLE, 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 UNDISCOVERABLE.'
Severity Info
Condition NF Instance's status transitions to UNDISCOVERABLE.

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.7050
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 to verify if the NF has sent UNDISCOVERABLE status in NFRegister or NfUpdate requests or check Jaeger traces to see traces for incoming requests.
  2. If there is no such incoming request, collect the logs 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