3.1.3 SCPInstanceDown

Table 3-4 SCPInstanceDown

Field Description
Severity Critical
Conditions kube_pod_status_ready{pod =~ '.*scp-worker.*|.*scpc-notification.*|.*scpc-subscription.*|.*scpc-configuration.*|.*scpc-audit.*|,|.*scpc-alternate-resolution.*|,condition =~ 'true'} !=1
OID used for SNMP Traps 1.3.6.1.4.1.323.5.3.35.1.2.7006
Description Notify that if any pod in ocscp release is down. Provides information like pod name, instance id and app name.
Recommended Actions
Cause: When the following issues occur:
  • The Control plane pods, such as configuration, subscription, notification, audit, and alternate-resolution are down due to connection failure with DB.

  • Pod restarts due to kubernetes liveliness or readiness probe failures.

  • Application restarts or starts failure.
Diagnostic Information:
  • Check if DB services are active by running the following command:
    kubectl describe pod <podname> -n <namespace>
  • Check kubernetes events for probe failures in the platform logs.
  • Check if any exception is reported in the SCP application logs.

Recovery: This alert is cleared automatically when the inactive pod is active. Recover DB services if down. Collect the application logs and contact My Oracle Support for any assistance.