Viewing Default Metric Charts


  • IAM policies: Viewing metric charts is part of monitoring. To monitor resources, you must be given 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've been granted and which compartment  you should work in. For more information about user authorizations for monitoring, see IAM Policies (Monitoring). Administrators: For common policies that give groups access to metrics, see Metric Access for Groups.
  • 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.

Example Metric Chart

The following image shows several metric streams in the graph view of a metric chart. Each metric stream corresponds to a compute instance.

The 85% value at 1:30 indicates that a compute instance used 85% of its CPU (averaged over the specified interval). Absent values are indicated for a metric stream toward the bottom of the graph, indicating that a compute instance didn't emit metric data until 1:30.

Metric streams and values in a graph.

Very small or large values are indicated by International System of Units (SI units), such as M for mega (10 to the sixth power). Units correspond to the selected metric and don’t change by statistic .

For more information about this example, see Example Query and Metric Chart.