Table: oci_nosql_table_metric_write_throttle_count - Query OCI NoSQL Database Tables using SQL

The OCI NoSQL Database is a fully managed NoSQL database service for modern application development. It offers flexible and cost-effective data management for any scale of real-time, high-volume, key-value workloads. The service ensures predictable low latencies for reads and writes, and offers SQL-like query capabilities.

Table Usage Guide

The oci_nosql_table_metric_write_throttle_count table provides insights into the write throttle counts for OCI NoSQL Database Tables. As a Database Administrator or Developer, explore details about the write throttle counts through this table, which can be useful to understand the performance of your NoSQL database tables. Utilize it to uncover information about the frequency of write throttle events, which can help in optimizing the performance and cost of your NoSQL databases.

Examples

Basic info

Explore the metrics related to write throttle counts in NoSQL tables to understand usage patterns and identify potential bottlenecks. This can aid in optimizing table configurations for improved performance.

select
  name,
  timestamp,
  minimum,
  maximum,
  average,
  sum,
  sample_count
from
  oci_nosql_table_metric_write_throttle_count
order by
  name,
  timestamp;

select
  name,
  timestamp,
  minimum,
  maximum,
  average,
  sum,
  sample_count
from
  oci_nosql_table_metric_write_throttle_count
order by
  name,
  timestamp;

Intervals where write throttle count exceeded 100 average

Determine the intervals where the write throttle count exceeded an average of 100. This can help identify periods of high demand or potential performance issues.

select
  name,
  timestamp,
  minimum,
  maximum,
  average,
  sum,
  sample_count
from
  oci_nosql_table_metric_write_throttle_count
where
  average > 100
order by
  name,
  timestamp;

The given PostgreSQL query does not use any PostgreSQL - specific functions
or data types,
and does not involve any JSON functions
or
join operations.Therefore,
it can be used in SQLite without any changes.Here is the SQLite query: ` ` ` sql
select
  name,
  timestamp,
  minimum,
  maximum,
  average,
  sum,
  sample_count
from
  oci_nosql_table_metric_write_throttle_count
where
  average > 100
order by
  name,
  timestamp;

Schema for oci_nosql_table_metric_write_throttle_count

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.
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.
name	text		The name of the NoSQL table.
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_nosql_table_metric_write_throttle_count