Resource Monitoring

• IAM policies: To monitor resources, you must have the required type of access in a policy  written by an administrator, whether you're using the Console or the REST API with an SDK, CLI, or other tool. The policy must give you access to the monitoring services as well as the resources being monitored. If you try to perform an action and get a message that you don't have permission or are unauthorized, confirm with your administrator the type of access you have and which compartment  you should work in. For more information about user authorizations for monitoring, see IAM Policies (Monitoring).
• Metrics exist in Monitoring: The resources that you want to monitor must emit metrics to the Monitoring service.
• Compute instances: To emit metrics, the Compute Instance Monitoring plugin must be enabled on the instance, and plugins must be running. The instance must also have either a service gateway or a public IP address to send metrics to the Monitoring service. For more information, see Enabling Monitoring for Compute Instances.

Not all resources support monitoring. See Supported Services for the list of resources that support the Monitoring service, which is required for queries and alarms used in monitoring.

The following pages describe basic resource monitoring tasks:

• Viewing Default Metric Charts for a Single Resource
• Viewing Default Metric Charts for a Metric Namespace (Multiple Resources)
• Creating a Query
• Creating an Alarm from a Default Metric Chart