Monitored Resources are not available.

• Monitored Resources (Compute view)
  1. Review the setup steps. See Getting Started with Resource Discovery and Monitoring.
  2. Verify that the application you are running is in the list of supported resource types. See Monitor Resources.
• Monitored Resources (Global view)
  1. Review the setup steps. See Getting Started with Resource Discovery and Monitoring.
  2. Verify that the application you are running is in the list of supported resource types. See Monitor Resources.

Top Processes are not available.

1. Make sure the Compute instance is running.
2. Ensure that you've completed all the setup and configuration steps.
3. Verify that Management Agent is running. From the OCI console, click Observability and Management Under Management Agent, click Agents.

You set up everything correctly, but don't have any supported resource types in your Compute instance(s).

If you don't have any supported resource types, you can still use the Resource Discovery and Monitoring Top Processes functionality to monitor what's running on the OCI Compute instance.

For a list of supported resource types, see Monitor Resources.

Dynamic Group Membership Limitation

If a Compute instance is a member of more than five dynamic groups, then no services that require dynamic groups will work. For more information about this limitation, see Managing Dynamic Groups.

Automatic activation fails.

If the automatic activation fails, ensure prerequisite polices have been defined correctly and that your Linux instance is running Oracle Cloud Agent 1.14 or later

New instances created via custom image do not auto-activate the Resource Discovery and Monitoring feature.

1. Check the policies are correctly setup for the compartment(s) where you are creating your new instances.
2. If your Linux instance from which you created the image is already activated, you must do following extra cleanup step before creating the image. Delete the /var/lib/oracle-cloud-agent/plugins/osms/.osms_im_ready file, then create your image.

Validation: When you create a new instance from your custom image, the file /var/lib/oracle-cloud-agent/plugins/osms/.osms_im_ready does not yet exist. It's created once the instance automatically activates, provided the required polices have been set up.