Skip to main content
Version: NG-2.16

OCI Autonomous Database

Introduction

OCI Autonomous Database is a fully managed, self-driving database service from Oracle Cloud that automates provisioning, tuning, backups, and scaling. It supports both transactional and analytical workloads with minimal administrative effort.

Getting Started

Compatibility

vuSmartMaps supports the monitoring of OCI Autonomous Database for availability, CPU and storage utilization, session trends, query performance, and connection reliability.

Data Collection Method

vuSmartMaps collects OCI Autonomous Database metrics using an internal data collector. This agent collects data based on the source configuration.

Prerequisites

Dependent Configuration

To configure this O11ySource, create a 'credential' of type 'oci' under the 'Definition' tab.

Inputs for Configuring Data Source

  • Compartment ID: The unique identifier (OCID) of the compartment in which your Autonomous Database resources are located.
  • Region: The OCI region where your resources are located.
  • Credential: The tenancy, user, and PEM file required for authentication with OCI.
  • Interval (in minutes): Time interval for polling data from the OCI Autonomous Database. Period should be between 5m – 60m.
  • Rate Limit: The Maximum requests per second. Note that the global default OCI rate limit is 5 reqs/sec.

Firewall Requirement

To collect data from this O11ySource, ensure the following ports are opened:

Source IPDestination IPDestination PortProtocolDirection
vuSmartMaps IPOCI Autonomous Database ListMetrics and SummarizeMetricsData API443*TCPOutbound

*Before providing the firewall requirements, please update the port based on the customer environment.

Configuring the Target

The User account provided in the configuration must have the minimum permissions listed below to collect metrics for all OCI Autonomous Database instances:


Allow group <group name> to inspect metrics in compartment <compartment name>


Allow group <group name> to read metrics in compartment <compartment name>

See also: Permissions Required for Each API Operation

Note: Because the configuration requires the Compartment ID & Region, a new endpoint or monitoring configuration will need to be created to monitor a new region or compartment for OCI Autonomous Database.

Refer to Oracle documentation for details on how to set up the monitoring endpoint access:

OCI API concepts API signing key handling Required Keys and OCIDs

Configuration Steps

  • Before configuring OCI Autonomous Database O11ysource, you must create a 'credential' of type 'OCI' under 'Definition' tab:
  • *Name: The name of the credentials.
  • *Tenancy: The OCID of your OCI tenancy, which acts as the root container for all your OCI resources.
  • *User: The OCID of the user that will be used for authentication in API requests.
  • *Fingerprint: A unique identifier for the public key associated with the API signing key of the user.
  • *Private Key File: RSA key pair in string format. You can use the following command to convert the PEM format file into a single line string.

awk 'NF {sub(/\r/, """"); printf ""%s\\n"",$0;}' <path to API Key>

  • Enable the O11ySource.
  • Select the sources tab and press the + button to add a new instance that has to be monitored.
  • Provide the required configurations:
  • *Compartment ID
  • *Region
  • *Credential
  • *Interval (in minutes)
  • *Rate Limit (Change only if required)
  • Click Save to close the data source window.

Metrics Collected

NameDescriptionData Type
TimestampTime when the metric was collected.DateTime64
Tenant IDUnique identifier for the tenant in OCI.String
Business Unit IDIdentifier of the associated business unit.String
Resource IDUnique identifier for the monitored resource.String
Database NameName of the Autonomous Database instance.String
Metric NameDisplay name of the metric being measured.String
RegionOCI region where the resource is deployed.String
Compartment IDOCI compartment containing the resource.String
Resource TypeType/category of the resource.String
Host NameName of the host server.String
Instance TypeType of database instance.String
CPU Utilization (%)Average CPU usage percentage.Float64
Storage Utilization (%)Average storage utilization percentage.Float64
Database Time (ms)Average database execution time.Float64
Wait Time (ms)Average database wait time.Float64
CPU Time (ms)Average CPU time consumed by sessions.Float64
Database AvailabilityIndicates database availability (0=downFloat64
Connection Latency (ms)Maximum latency for database connections.Float64
Query Latency (ms)Maximum query execution latency.Float64
Total SessionsTotal number of database sessions.Float64
Running StatementsAverage number of concurrently running SQL statements.Float64
Queued StatementsTotal queued SQL statements.Float64
Current LogonsMaximum active logins to the database.UInt32
User CallsTotal user call operations.UInt32
Failed LogonsAverage number of failed login attempts.Float64
User CommitsTotal number of commit operations.UInt32
User RollbacksTotal number of rollback operations.UInt32
DB Block ChangesTotal changes to database blocks.UInt32
Physical ReadsTotal number of physical read operations.UInt32
Physical WritesTotal number of physical write operations.UInt32
SQL*Net Bytes From ClientTotal bytes received from client via SQL*Net.UInt32
SQL*Net Bytes To ClientTotal bytes sent to client via SQL*Net.UInt32
APEX Page EventsTotal number of APEX page events.UInt32
APEX Page Load Time (ms)Total APEX page load time.UInt32
Peer LagMaximum replication lag between peer databases.UInt32
Average Active SessionsAverage active sessions over the interval.Float64
Blocking SessionsMaximum number of blocking sessions.UInt32
Execute CountTotal executed SQL statements.UInt32
Hard Parse CountTotal hard parse operations.UInt32
Logical ReadsTotal logical read operations.UInt32
Parse CountTotal SQL parse operations.UInt32
Parse Failure CountTotal failed SQL parse operations.UInt32
Physical Read Total BytesTotal bytes read physically from disk.UInt32
Physical Write Total BytesTotal bytes written physically to disk.UInt32
Redo GeneratedTotal redo log generated.UInt32
Session Utilization (%)Average session usage relative to capacity.UInt32
SQL*Net Bytes From DB LinkBytes received over database link.UInt32
SQL*Net Bytes To DB LinkBytes sent over database link.UInt32
Transaction CountTotal number of database transactions.UInt32
Storage Allocated (GB)Maximum allocated storage in GB.UInt32
Maximum Storage (GB)Maximum possible storage for the instance.UInt32
Storage Used (GB)Maximum storage used.UInt32
Logical Reads CountCount of logical read operations.UInt32
Connections Dropped by ClientTotal connections dropped by client.UInt32
Connections Dropped by ServerTotal connections dropped by server.UInt32
Failed ConnectionsTotal failed connection attempts.UInt32
Autonomous DB TypeType of databaseString
Deployment TypeType of database deploymentString