Oracle Autonomous Database on OCI extension
- Latest Dynatrace
- Extension
- Published Oct 27, 2025
Monitor health and performance of the Oracle Autonomous Database.
Get started
Overview
This extension monitors basics of the Oracle Autonomous Database, providing server-side observability on the database engine availability and performance level. This extension provides a light alternative to the Oracle Database monitoring extension that is compatible with OCI Autonomous DB.
This extension is executed by the ActiveGate (remote monitoring). You must have an ActiveGate provisioned in your environment and networking set up so the ActiveGate can connect to the subject OCI tenant containing the Autonomous Database you are about to monitor.
Use cases
- Monitor availability of the Autonomous DB and the underlying Oracle Cloud Infrastructure health.
- Track usage of the database storage and network resources.
- Track database usage in terms of users, logins, sessions, number of queries executed.
- Understand the resource impact that your applications have on the Autonomous DB, including wait times.
- Understand the impact that databse-side resource shortages have on your application.
Compatibility information
- OCI API access from ActiveGate is required
Activation and setup
To start, activate the extension in your environment using the in-product Hub. Then provide your OCI monitoring endpoint whereabouts. You will need to provide:
- Compartment ID
- Tenancy
- User
- Fingerprint
- Region
- Path location of a PEM key file which extension will use to sign OCI monitoring API requests
The User account provided in the configuration must also have the minimum permissions listed below to collect metrics for all feature sets.
- Allow group <group name> to read metrics in compartment <compartment name>
The PEM key file will need to be placed on any ActiveGate that is running the extension, in a location that is accessible to the extension. The recommended default location for the PEM file is:
- Linux:
<CONFIG>/remotepluginmodule/agent/conf/certificates/(default: /var/lib/dynatrace/remotepluginmodule/agent/conf/certificates/)
- Windows:
%PROGRAMDATA%\dynatrace\remotepluginmodule\agent\conf\certificates
See Oracle documentation for details on how to set up the monitoring endpoint access:
Details
This extension is built on top of the Extension Framework 2.0 and delivers:
- Metrics retrieved from the OCI API (extension internally uses Python to connect to the OCI API)
- A Dashboard
- Topology definition
- Unified Analysis screens
Feature sets
When activating your extension using monitoring configuration, you can limit monitoring to one of the feature sets. To work properly the extension has to collect at least one metric after the activation.
In highly segmented networks, feature sets can reflect the segments of your environment. Then, when you create a monitoring configuration, you can select a feature set and a corresponding ActiveGate group that can connect to this particular segment.
All metrics that aren't categorized into any feature set are considered to be the default and are always reported.
A metric inherits the feature set of a subgroup, which in turn inherits the feature set of a group. Also, the feature set defined on the metric level overrides the feature set defined on the subgroup level, which in turn overrides the feature set defined on the group level.
| Metric name | Metric key | Description |
|---|---|---|
| Sessions | cloud.oci.database.autonomous.sessions | Number of sessions in the database. |
| Execute Count | cloud.oci.database.autonomous.executes | Number of user and recursive calls that executed SQL statements. |
| Running Statements | cloud.oci.database.autonomous.running_statements | Number of running SQL statements aggregated accross all consumer groups. |
| Queued Statements | cloud.oci.database.autonomous.queued_statements | Number of queued SQL statements aggregated accross all consumer groups. |
| Transaction Count | cloud.oci.database.autonomous.transactions | Combined number of user commits and user rollbacks. |
| Current Logons | cloud.oci.database.autonomous.current_logons | Number of successful logons. |
| User Calls | cloud.oci.database.autonomous.user_calls | Combined number of logons, parses, and execute calls. |
| Total Parse Count | cloud.oci.database.autonomous.parses | Number of hard and soft parses. |
| Failed Logons | cloud.oci.database.autonomous.failed_logons | Number of logons that failed due to an invalid username and/or password. |
| Failed Connections | cloud.oci.database.autonomous.failed_connections | Number of failed database connections. |
| User Commits | cloud.oci.database.autonomous.user_commits | Number of user commits. |
| User Rollbacks | cloud.oci.database.autonomous.user_rollbacks | Number of times users manually issue the ROLLBACK statement or an error occurs during user's transactions. |
| Redo Size | cloud.oci.database.autonomous.redo_size | Amount of redo generated in bytes. |
| Hard Parse Count | cloud.oci.database.autonomous.hard_parses | Number of parse calls (real parses). |
| Failures Parse Count | cloud.oci.database.autonomous.failed_parses | Number of parse failures. |
| Bytes Received via SQL*Net from DBLink | cloud.oci.database.autonomous.sql_net_bytes_from_dblink | Number of bytes received from a database link over Oracle Net Services. |
| Bytes Sent via SQL*Net to DBLink | cloud.oci.database.autonomous.sql_net_bytes_to_dblink | Number of bytes sent over a database link over Oracle Net Services. |
| Bytes Received via SQL*Net from Client | cloud.oci.database.autonomous.sql_net_bytes_from_client | Number of bytes received from the client over Oracle Net Services. |
| Bytes Sent via SQL*Net to Client | cloud.oci.database.autonomous.sql_net_bytes_to_client | Number of bytes sent to the client from the foreground processes. |
| Metric name | Metric key | Description |
|---|---|---|
| CPU Utilization | cloud.oci.database.autonomous.cpu_util | CPU utilization aggregated across all consumer groups. |
| Storage Utilization | cloud.oci.database.autonomous.storage_util | Percentage of provisioned storage capacity currently in use. |
| Maximum Storage Space | cloud.oci.database.autonomous.max_storage_space | Maximum amount of storage reserved for the database. |
| Storage Space Allocated | cloud.oci.database.autonomous.storage_space_allocated | Space allocated to the database. |
| Storage Space Used | cloud.oci.database.autonomous.storage_space_used | Space used by the database. |
| DB Time | cloud.oci.database.autonomous.db_time | Rate of accumulation of database time (CPU + Wait) by foreground sessions. |
| Wait Time | cloud.oci.database.autonomous.wait_time | Average rate of accumulation of non-idle wait time by foreground sessions. |
| CPU Time | cloud.oci.database.autonomous.cpu_time | Rate of accumulation of CPU time by foreground sessions. |
| Database Availability | cloud.oci.database.autonomous.database_availability | Database availability for connections (1 = DB Available, 0 = DB Unavailable). |
| Connection Latency | cloud.oci.database.autonomous.connection_latency | Time taken to connect to a ADB-S database in each region from a VM in the same region. |
| Query Latency | cloud.oci.database.autonomous.query_latency | Time taken to display results of a simple query. |
| Session Logical Reads | cloud.oci.database.autonomous.session_logical_reads | Sum of "db block gets" plus "consistent gets". |
| DB Block Changes | cloud.oci.database.autonomous.db_block_changes | Number of changes that where part of an update or delete operation to all blocks in SGA. |
| Physical Reads | cloud.oci.database.autonomous.physical_reads | Number of data blocks read from disk. |
| Physical Writes | cloud.oci.database.autonomous.physical_writes | Number of data blocks written to disk. |
| Physical Read Total Bytes | cloud.oci.database.autonomous.physical_read_bytes | Size in bytes of disk reads by all database instance activity. |
| Physical Write Total Bytes | cloud.oci.database.autonomous.physical_write_bytes | Size in bytes of disk writes by all database instance activity. |
| Metric name | Metric key | Description |
|---|---|---|
| APEX Page Events | cloud.oci.database.autonomous.apex_page_events | Number of APEX page events. |
| APEX Page Load Time | cloud.oci.database.autonomous.apex_page_load_time | Average APEX page execution time. |
| Active APEX Applications | cloud.oci.database.autonomous.apex_active_applications | Number of APEX applications with activity. |
| APEX Workspace Count | cloud.oci.database.autonomous.apex_workspaces | Total number of user-created workspaces. |
FAQ
This extension offers a lightweight, limited alternative to the Oracle Database monitoring extension, specifically for the Autonomous DB on OCI.
This extension lets you monitor basics of the database performance, using alternative REST API source of metrics provided by the Oracle Cloud Infrastructure APIs.
Oracle Database monitoring extension does not support Autonomous DB on OCI. This limitation roots down to the Oracle SQL data source that doesn't support certificate-based authentication, which OCI requires.
Query-level statistics are not available in this extension. Use OneAgent on your app servers to obtain insight into SQL queries that your app servers execute against the Autonomous DB.
No. This extension provides a subset of metrics that the Oracle Database extension offers.
Yes. See Oracle Cloud Infrastructure hub tile for details on how proxy support works with OCI.
Metric to DDU consumption multiplier for each Autonomous Database monitored is:
40 * 525.6 DDUs/year
DDU cost above does not include any possible Log events or Custom events triggered by the extension. For more information on this, please visit the DDU log event cost and DDU custom event cost pages.
