Table: oci_database_autonomous_db_metric_cpu_utilization_daily - Query OCI Database Autonomous Databases using SQL
Oracle Autonomous Database is a fully managed, preconfigured database environment with two workload types available, Autonomous Transaction Processing and Autonomous Data Warehouse. The autonomous database is built on Oracle Database 19c and includes features like automatic indexing, AI-driven tuning, and automated data movement. It is designed to support all standard SQL and business intelligence (BI) tools and provides all of the performance of the market-leading Oracle Database in an environment that is tuned and optimized for data warehouse workloads.
Table Usage Guide
The oci_database_autonomous_db_metric_cpu_utilization_daily
table provides insights into daily CPU Utilization Metrics of Autonomous Databases within Oracle Cloud Infrastructure. As a Database Administrator, explore database-specific details through this table, including CPU utilization, average active sessions, and associated metadata. Utilize it to monitor and optimize the performance of your Autonomous Databases, such as identifying databases with high CPU utilization, and making informed decisions on resource allocation.
Examples
Basic info
Analyze the daily CPU utilization metrics of your autonomous databases to understand their performance trends and resource consumption. This can assist in optimizing resource allocation, identifying peak usage times, and planning capacity for better database management.
select id, timestamp, minimum, maximum, average, sample_countfrom oci_database_autonomous_db_metric_cpu_utilization_dailyorder by id, timestamp;
select id, timestamp, minimum, maximum, average, sample_countfrom oci_database_autonomous_db_metric_cpu_utilization_dailyorder by id, timestamp;
CPU Over 80% average
Identify instances where the average CPU utilization exceeds 80% in a day to monitor system performance and prevent potential overloads or slowdowns. This allows for proactive resource management and can help maintain optimal system operation.
select id, timestamp, round(minimum :: numeric, 2) as min_cpu, round(maximum :: numeric, 2) as max_cpu, round(average :: numeric, 2) as avg_cpu, sample_countfrom oci_database_autonomous_db_metric_cpu_utilization_dailywhere average > 80order by id, timestamp;
select id, timestamp, round(minimum, 2) as min_cpu, round(maximum, 2) as max_cpu, round(average, 2) as avg_cpu, sample_countfrom oci_database_autonomous_db_metric_cpu_utilization_dailywhere average > 80order by id, timestamp;
Query examples
Schema for oci_database_autonomous_db_metric_cpu_utilization_daily
Name | Type | Operators | Description |
---|---|---|---|
_ctx | jsonb | Steampipe context in JSON form. | |
average | double precision | The average of the metric values that correspond to the data point. | |
compartment_id | text | The ID of the compartment. | |
id | text | The OCID of the Autonomous Database. | |
maximum | double precision | The maximum metric value for the data point. | |
metric_name | text | The name of the metric. | |
minimum | double precision | The minimum metric value for the data point. | |
namespace | text | The metric namespace. | |
region | text | The OCI region in which the resource is located. | |
sample_count | double precision | The number of metric values that contributed to the aggregate value of this data point. | |
sp_connection_name | text | =, !=, ~~, ~~*, !~~, !~~* | Steampipe connection name. |
sp_ctx | jsonb | Steampipe context in JSON form. | |
sum | double precision | The sum of the metric values for the data point. | |
tenant_id | text | =, !=, ~~, ~~*, !~~, !~~* | The OCID of the Tenant in which the resource is located. |
tenant_name | text | The name of the Tenant in which the resource is located. | |
timestamp | timestamp with time zone | The time stamp used for the data point. | |
unit | text | The standard unit for the data point. |
Export
This table is available as a standalone Exporter CLI. Steampipe exporters are stand-alone binaries that allow you to extract data using Steampipe plugins without a database.
You can download the tarball for your platform from the Releases page, but it is simplest to install them with the steampipe_export_installer.sh
script:
/bin/sh -c "$(curl -fsSL https://steampipe.io/install/export.sh)" -- oci
You can pass the configuration to the command with the --config
argument:
steampipe_export_oci --config '<your_config>' oci_database_autonomous_db_metric_cpu_utilization_daily