1. Using Oracle CASB Cloud Service
  2. Setting Up Cloud Applications for Monitoring
  3. Registering Cloud Applications with Oracle CASB Cloud Service
  4. Resuming Monitoring that Has Stopped

Resuming Monitoring that Has Stopped

Understand how to tell that monitoring has stopped, and how to troubleshoot the problem so that monitoring can resume.

Oracle CASB Cloud Service can, at times, be unable to monitor an application instance after you register it, or monitoring can stop after working for some time.

Often, this is due to the Oracle CASB Cloud Service user's credentials expiring or being replaced in the application instance. At other times, this can be due to a transitory or more pervasive network issue.

When monitoring stops, Oracle CASB Cloud Service displays a “no” symbol Image of the “no” symbol below the application instance icon in the Dashboard. You or another administrator receive an email notification.

  1. Select the Dashboard from the Navigation menu. If the Navigation Menu is not displayed, click the Navigation Menu icon Image of the Navigation Menu icon. to display it.

  2. Hover over the tile for the application that is no longer being monitored.

    This icon has a “no” symbol Image of the “no” symbol below it. The Health Summary card for the application appears.

  3. For additional information about the inability to access the application instance, click the More > link in the monitoring failure message in the Health Summary card .

    The common issues include:

    • Someone updated the credentials (for example, the password) for the Oracle CASB Cloud Service user in the cloud service, but not in the Oracle CASB Cloud Service console.

    • The credentials for the Oracle CASB Cloud Service user expired in the cloud service, and they need to be updated there and in the Oracle CASB Cloud Service console.

    • The Oracle CASB Cloud Service user needs administrator privileges. See Preparing Cloud Applications for Monitoring.