3.2.36 ScpWorkerPodCpuUtilizationAboveCriticalThreshold

Table 3-40 ScpWorkerPodCpuUtilizationAboveCriticalThreshold

Field Details
Description CPU utilization of SCP worker at critical level
Summary Worker CPU utilization lead to critical level. 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 CPU utilization of scp-worker reaches the CRITICAL level.

increase(ocscp_worker_pod_overload_control_cpu_utilization_total{ocscp_threshold_level="CRITICAL"}[2m]) > 0

OID 1.3.6.1.4.1.323.5.3.35.1.2.7021
Metric Used ocscp_worker_pod_overload_control_cpu_utilization_total
Recommended Action

Cause: When CPU utilization of scp-worker reaches the CRITICAL level.

Diagnostic Information:
  1. Get the configured threshold level values using Pod Overload Control Policy REST APIs. For more information about Pod Overload Control Policy, see Oracle Communications Cloud Native Core, Service Communication Proxy REST Specification Guide.
  2. Check the CPU threshold level status from the scp-worker pod logs under the warn level.

Recovery:

  • Reduce the incoming service request rate.
  • This alert is automatically cleared when CPU utilization is reduced to below CRITICAL threshold level.

For any assistance, contact My Oracle Support.