3.2.54 SCPWorkerQueuesUtilizationAboveCriticalThreshold

Table 3-58 SCPWorkerQueuesUtilizationAboveCriticalThreshold

Field Details
Description 'instancename: {{$labels.instance}}, namespace: {{$labels.kubernetes_namespace}}, podname: {{$labels.kubernetes_pod_name}}: SCP Worker Queues Utilization Above Critical Threshold'
Summary 'SCP Worker Queues Utilization Above Critical Threshold, instancename: {{$labels.instance}}, namespace: {{$labels.kubernetes_namespace}}, podname: {{$labels.kubernetes_pod_name}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }}'
Severity Critical
Condition This alert is raised when task queues in scp-worker service are utilized above 85% of the maximum size (user configure critical threshold value).

ocscp_worker_queue_alert{severity="CRITICAL"} == 1
OID 1.3.6.1.4.1.323.5.3.35.1.2.9007
Metric Used ocscp_worker_queue_alert
Recommended Action

Cause: Worker task queues are getting filled and the traffic is more than expected.

Diagnostic Information:
  1. Monitor traffic towards nrfProxy to pod using the KPI dashboard.
  2. Refer to rate of the following metric on the Grafana dashboard: ocscp_worker_queue_utilization

Recovery: This alert clears automatically when the traffic goes below critical threshold.

For any assistance, contact My Oracle Support.