Database Metrics

You can monitor the health, capacity, and performance of your Oracle Cloud Infrastructure Database service resources by using metrics , alarms , and notifications. For more information, see Monitoring Overview and Notifications Overview.

This topic describes the metrics emitted by the Database service in the oci_autonomous_database namespace.

Resources: Autonomous Databases.

Overview of the Database Service Autonomous Database Metrics

The Database service metrics help you measure useful quantitative data about your Autonomous Databases, such as CPU and storage utilization, the number of successful and failed database logon and connection attempts, database operations, SQL queries, and transactions, and so on. You can use metrics data to diagnose and troubleshoot problems with Autonomous Databases. For a complete list of available metrics for Autonomous Databases, see Available Metrics: oci_autonomous_database.

To view a default set of metrics charts in the Console, navigate to the Autonomous Database that you're interested in, and then click Metrics. You also can use the Monitoring service to create custom queries.

Prerequisites

IAM policies: 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 on user authorizations for monitoring, see the Authentication and Authorization section for the related service: Monitoring or Notifications.

Available Metrics: oci_autonomous_database

The metrics listed in the following table are automatically available for any Autonomous Database that you create. You do not need to enable monitoring on the resource to get these metrics.

Note

Valid alarm intervals are 5 minutes or greater due to the frequency at which these metrics are emitted. See To create an alarm for details on creating alarms.

Database service metrics for Autonomous Databases include the following dimensions :

AUTONOMOUSDBTYPE
The type of Autonomous Database, Autonomous Data Warehouse (ADW) or Autonomous Transaction Processing (ATP).
deploymentType
The Exadata infrastructure type, shared or dedicated. When using the Console to view default metric charts for multiple Autonomous Databases, you must specify this dimension.
DISPLAYNAME
The friendly name of the Autonomous Database.
REGION
The region  in which the Autonomous Database resides.
RESOURCEID
The OCID  of the Autonomous Database.
RESOURCENAME
The name of the Autonomous Database.

In the following table, metrics that are marked with an asterisk (*) can be viewed only on the Service Metrics page of the Oracle Cloud Infrastructure Console. All metrics can be filtered by the dimensions described in this topic. Note that some metrics are only available for Autonomous Databases using either shared Exadata infrastructure or dedicated Exadata infrastructure. This is indicated in the Applicable Exadata Infrastructure Type column.

Metric Metric Display Name Unit Description Applicable Exadata Infrastructure Type
ConnectionLatency Connection Latency Milliseconds The time taken to connect to a Autonomous Database that uses shared Exadata infrastructure in each region from a Compute service virtual machine in the same region. Shared only
CpuTime* CPU Time Seconds per second Average rate of accumulation of CPU time by foreground sessions in the database over the time interval. The CPU time component of Average Active Sessions.

Dedicated only

CpuUtilization CPU Utilization percent The CPU usage expressed as a percentage, aggregated across all consumer groups. The utilization percentage is reported with respect to the number of CPUs the database is allowed to use, which is two times the number of OCPUs. Both
CurrentLogons* Current Logons count The number of successful logons during the selected interval. Both

DBTime*

DB Time seconds per second The amount of time database user sessions spend executing database code (CPU Time + WaitTime). DB Time is used to infer database call latency, because DB Time increases in direct proportion to both database call latency (response time) and call volume. It is calculated as the average rate of accumulation of database time by foreground sessions in the database over the time interval. Also known as Average Active Sessions.

Dedicated only

ExecuteCount Execute Count count The number of user and recursive calls that executed SQL statements during the selected interval. Both

FailedConnections*

Failed Connections count The number of failed database connections.

Shared only

FailedLogons

Failed Logons count The number of logons that failed because of an invalid username and/or password, during the selected interval.

Shared only

ParseCount* Parse Count (Total) count The number of hard and soft parses during the selected interval. Both
QueryLatency Query Latency Milliseconds The time taken to display the results of a simple query on the user's screen. Shared only
QueuedStatements Queued Statements count The number of queued SQL statements, aggregated across all consumer groups, during the selected interval. Both
RunningStatements Running Statements count The number of running SQL statements, aggregated across all consumer groups, during the selected interval. Both
Sessions Sessions count The number of sessions in the database. Both

StorageAllocated*

Storage Space Allocated GB Maximum amount of space allocated to the database during the interval.

Dedicated only

StorageAllocatedByTablespace*

Allocated Storage Space By Tablespace GB Maximum amount of space allocated for each tablespace during the interval.

Dedicated only

StorageUsed*

Storage Space Used GB Maximum amount of space used during the interval.

Dedicated only

StorageUsedByTablespace*

Storage Space Used By Tablespace GB Maximum amount of space used by each tablespace during the interval.

Dedicated only

StorageUtilization Storage Utilization percent The percentage of provisioned storage capacity currently in use. Represents the total allocated space for all tablespaces. Both

StorageUtilizationByTablespace*

Storage Space Utilization By Tablespace percent The percentage of space utilized by each tablespace.

Dedicated only

TransactionCount* Transaction Count count The combined number of user commits and user rollbacks during the selected interval. Both
UserCalls* User Calls count The combined number of logons, parses, and execute calls during the selected interval. Both

WaitTime*

Wait Time Seconds per second Average rate of accumulation of non-idle wait time by foreground sessions in the database over the time interval. The wait time component of Average Active Sessions.

Dedicated only

Using the Console

To view default metric charts for a single Autonomous Database
  1. Open the navigation menu. Under Database, click Autonomous Transaction Processing or Autonomous Data Warehouse.
  2. Choose the Compartment that contains the Autonomous Database you want to view, and then click display name of the database to view its details.
  3. Under Resources, click Metrics.

    The Metrics page displays a default set of charts for the current Autonomous Database. See Available Metrics: oci_autonomous_database for information about the default charts.

For more information about monitoring metrics and using alarms, see Monitoring Overview. For information about notifications for alarms, see Notifications Overview.

To view default metric charts for multiple Autonomous Databases
  1. Open the navigation menu. Under Solutions and Platform, go to Monitoring and click Service Metrics.
  2. For Compartment, select the compartment that contains the Autonomous Databases that you're interested in.
  3. For Metric Namespace, select oci_autonomous_database.

    The Service Metrics page dynamically updates the page to show charts for each metric that is emitted by the selected metric namespace.

  4. For Dimensions, specify an Exadata infrastructure deployment type (shared or dedicated). Important: If you do not specify a deployment type, no service metrics will display on the page.

    Optionally, you can specify other dimensions to filter your displayed metrics. See To filter results and To select different resources in the Monitoring documentation for more information.

Tip

If there are multiple Autonomous Databases in the compartment, the charts default to show a separate line for each master encryption key. You can instead show a single line aggregated across all Autonomous Databases in the compartment by selecting the Aggregate Metric Streams check box.

For more information about monitoring metrics and using alarms, see Monitoring Overview. For information about notifications for alarms, see Notifications Overview.