Table: oci_mysql_db_system_metric_cpu_utilization_hourly - Query OCI MySQL DB System Metrics using SQL
Oracle Cloud Infrastructure's MySQL DB System is a fully managed, scalable MySQL relational database service that enables organizations to deploy cloud-native applications. It offers a secure, automated, and extensible platform for running MySQL applications. This service provides the ability to monitor CPU utilization metrics on an hourly basis.
Table Usage Guide
The oci_mysql_db_system_metric_cpu_utilization_hourly
table provides insights into the CPU utilization metrics of MySQL DB Systems within Oracle Cloud Infrastructure (OCI). As a database administrator, you can explore these metrics to understand the CPU usage patterns and performance of your MySQL DB Systems. Utilize it to uncover information about CPU usage trends, identify peak usage times, and plan capacity accordingly.
Examples
Basic info
Analyze the CPU utilization of your MySQL database system over the past hour. This allows you to identify periods of high demand and optimize system performance accordingly.
select id, timestamp, minimum, maximum, average, sample_countfrom oci_mysql_db_system_metric_cpu_utilization_hourlyorder by id, timestamp;
select id, timestamp, minimum, maximum, average, sample_countfrom oci_mysql_db_system_metric_cpu_utilization_hourlyorder by id, timestamp;
CPU Over 80% average
Analyze the settings to understand instances where CPU utilization is consistently high, exceeding 80% on average. This is useful for identifying potential performance bottlenecks and planning for capacity upgrades.
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_mysql_db_system_metric_cpu_utilization_hourlywhere 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_mysql_db_system_metric_cpu_utilization_hourlywhere average > 80order by id, timestamp;
Query examples
Schema for oci_mysql_db_system_metric_cpu_utilization_hourly
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 DB System. | |
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_mysql_db_system_metric_cpu_utilization_hourly