Table: oci_analytics_instance - Query OCI Analytics Instances using SQL
Oracle Cloud Infrastructure (OCI) Analytics Instances are part of the OCI Analytics service, which provides an integrated and robust data analytics solution. This service enables users to gather, explore, and analyze data from various sources, transforming it into insightful and actionable business information. It is designed to support all users, from data engineers to business users, with self-service data visualization, enterprise reporting, and augmented analytics.
Table Usage Guide
The oci_analytics_instance
table provides insights into OCI Analytics Instances. As a data analyst or business user, you can explore instance-specific details through this table, including current state, capacity, and associated metadata. Utilize it to uncover information about instances, such as those with high capacity, the network configurations of instances, and the verification of instance lifecycle states.
Examples
Basic info
Explore which analytics instances are currently active and when they were last modified. This can help in managing resources and identifying instances that may be outdated or unused.
select id, name, lifecycle_state as state, time_created, time_updatedfrom oci_analytics_instance;
select id, name, lifecycle_state as state, time_created, time_updatedfrom oci_analytics_instance;
List analytics instances which are not active
Explore which analytics instances are currently inactive. This can be useful for identifying unused resources and potential cost savings.
select id, name, lifecycle_state as state, time_created, time_updatedfrom oci_analytics_instancewhere lifecycle_state <> 'ACTIVE';
select id, name, lifecycle_state as state, time_created, time_updatedfrom oci_analytics_instancewhere lifecycle_state <> 'ACTIVE';
List analytics instances older than 90 days
Determine the areas in which analytics instances have been active for more than 90 days. This can be useful for assessing system usage and identifying potential areas for optimization or maintenance.
select id, name, lifecycle_state, time_created, time_updatedfrom oci_analytics_instancewhere time_created <= (current_date - interval '90' day)order by time_created;
select id, name, lifecycle_state, time_created, time_updatedfrom oci_analytics_instancewhere time_created <= date('now', '-90 day')order by time_created;
List analytics instances with private network endpoint type
Determine the areas in which analytics instances are configured with a private network endpoint. This can be useful for identifying instances that may have heightened security requirements or specific network configurations.
select id, name, lifecycle_state, network_endpoint_details, time_created, time_updatedfrom oci_analytics_instancewhere network_endpoint_details ->> 'networkEndpointType' = 'PRIVATE';
select id, name, lifecycle_state, network_endpoint_details, time_created, time_updatedfrom oci_analytics_instancewhere json_extract(network_endpoint_details, '$.networkEndpointType') = 'PRIVATE';
Schema for oci_analytics_instance
Name | Type | Operators | Description |
---|---|---|---|
_ctx | jsonb | Steampipe context in JSON form. | |
capacity_type | text | = | The analytics instance's capacity model to use. |
capacity_value | bigint | The analytics instance's capacity value selected. | |
compartment_id | text | = | The OCID of the compartment in Tenant in which the resource is located. |
defined_tags | jsonb | Defined tags for resource. Defined tags are set up in your tenancy by an administrator. Only users granted permission to work with the defined tags can apply them to resources. | |
description | text | The analytics instance's optional description. | |
email_notification | text | The email address receiving notifications. | |
feature_set | text | = | The analytics instance's feature set. |
freeform_tags | jsonb | Free-form tags for resource. This tags can be applied by any user with permissions on the resource. | |
id | text | = | The analytics instance's Oracle ID (OCID). |
license_type | text | The license used for the service. | |
lifecycle_state | text | = | The analytics instance's current state. |
name | text | = | A user-friendly name. Does not have to be unique, and it's changeable. |
network_endpoint_details | jsonb | The base representation of a network endpoint. | |
private_access_channels | jsonb | The private access channels of the analytics instance. | |
region | text | The OCI region in which the resource is located. | |
service_url | text | The URL of the Analytics service. | |
sp_connection_name | text | =, !=, ~~, ~~*, !~~, !~~* | Steampipe connection name. |
sp_ctx | jsonb | Steampipe context in JSON form. | |
tags | jsonb | A map of tags for the resource. | |
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. | |
time_created | timestamp with time zone | The date and time the instance was created. | |
time_updated | timestamp with time zone | The date and time the instance was last updated. | |
title | text | Title of the resource. | |
vanity_url_details | jsonb | The vanity url configuration details of the analytic instance. |
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_analytics_instance