5.3.5 OcnrfTotalNFsRegisteredBelowCriticalThreshold

Table 5-50 OcnrfTotalNFsRegisteredBelowCriticalThreshold

Field Details
Description 'Number of active registrations in OCNRF (current value is: {{ $value }}) is below critical threshold'
Summary kubernetes_namespace: {{$labels.kubernetes_namespace}},nrflevel:{{$labels.NrfLevel}}, podname: {{$labels.kubernetes_pod_name}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }} : Active registrations count.
Severity Critical
Condition The total number of NFs currently in "REGISTERED" state with the NRF is below the critical threshold.

Note: The threshold values are provided as an example. User can configure the threshold value as per the requirement.

OID 1.3.6.1.4.1.323.5.3.36.1.2.7042
Metric Used 'ocnrf_active_registrations_count'
Recommended Actions The alert is cleared when the number of registered NFs is above the critical threshold.
Steps:
  1. Check if there is traffic for requests other than registration (for example, discovery requests). This ensures that NRF FQDN is reachable from other NFs and Ingress Gateway is up and running.
  2. Check if Ingress Gateway pod is up and running:
    kubectl get po -n <namespace>
  3. Check for registration pod logs on Kibana for ERROR WARN logs.
  4. 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 how to collect logs using Data Collector tool, see Oracle Communications Cloud Native Core, cnDBTier User Guide.

Notes
  1. Operator can configure the threshold values with respect to the number of NFs expected within the network.
  2. NFs with NFStatus as 'SUSPENDED' or "UNDISCOVERABLE' are not considered as registered.
Available in OCI Yes