You can monitor the health, capacity, and performance of your Oracle Cloud Infrastructure Database service resources by using (Monitoring service) A measurement related to health, capacity, or performance of a given resource. Example: CpuUtilization, The trigger rule and query to evaluate and related configuration, such as notification details to use when the trigger is breached. Alarms passively monitor your cloud resources using metrics in Monitoring., and notifications. For more information, see Monitoring Overview and Notifications Overview.
Database metrics are currently available only for Autonomous Databases in serverless deployments.
This topic describes the metrics emitted by the Database service in the
Resources: Autonomous Databases.
Overview of the 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.
IAM policies: To monitor resources, you must be given the required type of access in a An IAM document that specifies who has what type of access to your resources. It is used in different ways: to mean an individual statement written in the policy language; to mean a collection of statements in a single, named "policy" document (which has an Oracle Cloud ID (OCID) assigned to it); and to mean the overall body of policies your organization uses to control access to resources. 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 A collection of related resources that can be accessed only by certain groups that have been given permission by an administrator in your organization. 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.
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.
Database service metrics for Autonomous Databases include the following (Monitoring service) A qualifier provided in a metric definition. Example: Resource identifier (resourceId), provided in the definitions of oci_computeagent metrics.:
- The type of Autonomous Database, Autonomous Data Warehouse (ADW) or Autonomous Transaction Processing (ATP).
- The friendly name of the Autonomous Database.
- The A collection of availability domains located in a single geographic location. in which the Autonomous Database resides.
- The An Oracle-assigned unique ID called an Oracle Cloud Identifier (OCID). This ID is included as part of the resource's information in both the Console and API. of the Autonomous Database.
- 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.
|Metric||Metric Display Name||Unit||Description||Dimensions|
||Current Logons||count||The number of successful logons during the selected interval.||
||CPU Utilization||percent||The CPU utilization 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.|
||Execute Count||count||The number of user and recursive calls that executed SQL statements during the selected interval.|
||Failed Connections||count||The number of failed database connections.|
||Failed Logons||count||The number of logons that failed because of an invalid username and/or password, during the selected interval.|
||Parse Count (Total)||count||The number of hard and soft parses during the selected interval.|
||Queued Statements||count||The number of queued SQL statements, aggregated across all consumer groups, during the selected interval.|
||Running Statements||count||The number of running SQL statements, aggregated across all consumer groups, during the selected interval.|
||Sessions||count||The number of sessions in the database.|
||Storage Utilization||percent||The percentage of provisioned storage capacity currently in use. Represents the total allocated space for all tablespaces.|
||Transaction Count||count||The combined number of user commits and user rollbacks during the selected interval.|
||User Calls||count||The combined number of logons, parses, and execute calls during the selected interval.|
Open the navigation menu. Under Database, click Autonomous Transaction Processing or Autonomous Data Warehouse.
- Choose the Compartment that contains the Autonomous Database you want to view, and then click display name of the database to view its details.
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.
- Open the navigation menu. Under Solutions and Platform, go to Monitoring and click Service Metrics.
- For Compartment, select the compartment that contains the Autonomous Databases that you're interested in.
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.
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.
Using the API
For information about using the API and signing requests, see REST APIs and Security Credentials. For information about SDKs, see Software Development Kits and Command Line Interface.
Use the following APIs for monitoring: