5.4.2.7 OcnrfOverloadThresholdBreachedL4

Table 5-77 OcnrfOverloadThresholdBreachedL4

Field Details
Description 'Overload Level of {{$labels.app_kubernetes_io_name}} service is L4'
Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}}, podname: {{$labels.kubernetes_pod_name}}: Overload Level of {{$labels.app_kubernetes_io_name}} service is L4'
Severity Warning
Condition NRF Services have breached its configured threshold of Level L4 for any of the aforementioned metrics. Thresholds are configured for CPU, svc_failure_count, svc_pending_count, and memory.
OID 1.3.6.1.4.1.323.5.3.36.1.2.7062
Metric Used load_level
Recommended Actions

The alert is cleared when the Ingress Traffic rate falls below the configured L4 threshold.

Note: The thresholds can be configured using REST API.

Steps:

  1. Reassess the reasons leading to NRF receiving additional traffic.
  2. Refer to alert to determine which service is receiving high traffic. It may be due to a sudden spike in traffic.

    For example: When one mated site goes down, the NFs move to the given site.

  3. Check the service pod logs on Kibana to determine the reason for the errors.
  4. If this is expected traffic, then the thresholds levels may be reevaluated as per the call rate and reconfigured as mentioned in Oracle Communications Cloud Native Core, Network Repository Function REST Specification Guide.
  5. If this is the unexpected traffic, contact My Oracle Support.
Available in OCI Yes