Network Function Service Query

NRF Client queries the status of the NF service matching the selectors specified in nrf.nfServiceQuery.selectors. If any combination of label and value is a match, the metrics of that pod are queried.

The system_cpu_count metric reports the number of CPUs available to the pod. The NF service capacity is the total number of CPUs across all available pods. The system_cpu_usage metric reports the percentage of CPUs used in the pod as a value between 0 and 1. The NF service load is reported as an integer from 0 to 100 representing the average CPU load as calculated from the average of the usage for each pod.

When no pods are found for the NF service or there is no capacity available (either through a reported capacity of 0, no metric endpoint, or a missing system_cpu_count), NRF Client determines that the NF service is not available and pauses heartbeat updates to the NRF. It is expected that the NRF will set the NF service to SUSPENDED itself, eventually. The NRF Client continues to check for the availability of the NF service and resumes heartbeats with an /nfStatus=REGISTERED when they become available again.