Oracle Database extension

• Latest Dynatrace
• Extension
• Updated on Apr 20, 2026

Collect Oracle Database metrics and audit logs to monitor performance and security.

1 of 4The Overview Dashboard is provided by the extension as an entry point to Oracle entities monitored across all configurations of the extension.

Get started

Overview

This remote extension runs on an ActiveGate within your environment. It connects to each Oracle Database you want to monitor, executes a series of queries on various views, and sends the collected data to Dynatrace.

Dynatrace automatically detects all applications and microservices in your system and their Oracle Database usage.

Dynatrace uses AI to diagnose anomalies in real time and identify root causes in slow-performing or erroneous SQL statements. Code-level insights combined with database server monitoring provide full-stack observability.

The Oracle Database extension provides server-side monitoring with availability and performance statistics, SQL statements, and log insights.

Use cases

Requirements

Compatibility information

The following Oracle versions are supported:

The following architectures are supported:

Activation and setup

Follow these steps to set up server-side monitoring for Oracle databases.

If your Oracle Database server runs on a virtual machine or bare metal, install OneAgent on it to start collecting system performance metrics.

To monitor Oracle Database server health and performance, activate the Oracle Database extension. The extension queries database performance views to collect metrics and events.

Add DB instance

Select hosting type

Select a hosting type from the options. This choice determines which script generates the necessary database objects later in the process.

Select ActiveGate group

Accept license agreement

The Oracle Database extension requires that you accept the Dynatrace redistribution license agreement for Oracle JDBC Driver.

Create a connection

Set up the connection to your database instance. Provide the required credentials directly in the wizard or use secure alternatives:

Install instance

Get started for Oracle Database clients

Follow these steps to set up client-side monitoring for Oracle databases.

Activate the following OneAgent features to gain full tracing insights:

Activate log monitoring

Activate log monitoring to get full log insight.

Details

Extension package

This extension package contains:

Licensing and cost

There is no charge for obtaining the extension, only for the data (metrics and logs) that the extension ingests. The details of license consumption depend on which licensing model you are using: either Dynatrace classic licensing or the Dynatrace Platform Subscription (DPS) model.

Dynatrace Platform Subscription

With a Dynatrace Platform Subscription (DPS) license:

Classic licensing

With a Dynatrace classic license:

Execution plan monitoring

For SaaS customers with access to Database Services Classic, the execution plan monitoring functionality is also available when analyzing statement performance.

For this feature to work, the DBMS_XPLAN package must be available, and the monitoring user must have permission to call the DISPLAY_CURSOR function. Per the official documentation, SELECT or READ permissions are required on the following views:

Sensitive data masking

Query performance tracking may expose sensitive data in reported statements. Dynatrace provides an optional mechanism to mask selected attributes. For details, see Log processing examples.

The following configurations show how to mask sensitive data in tracked statements:

DQL and logs

Audit log files tracking

Check log file's location

Add OneAgent Log module security rules

Configure OneAgent Log module security rules to allow access to local files by adding the oracle.json file:

{
    "@version": "1.0.0",
    "allowed-log-paths-configuration": [
        {
            "directory-pattern": "/u01/app/oracle/admin/oracle_standalone/adump/",
            "file-pattern": "*.aud",
            "action": "INCLUDE"
        }
    ]
}

No OneAgent restart is required. The configuration takes effect within 1 minute.

Configure custom log source and log ingest rules

Custom log source

Use the log file location from the first query, for example, /u01/app/oracle/admin/oracle_standalone/adump/*.

Log ingest rules

To capture only ORA-01017 (invalid username or password login attempts), configure the log ingest rule as follows:

Log content is any of: (.*)RETURNCODE:\[(\d+)\] "1017 AND Log source is any of:
/u01/app/oracle/admin/oracle_standalone/adump/*

Accessing logs

Access the collected logs using the following DQL query:

fetch logs
| filter matchesValue(log.source, "/u01/app/oracle/admin/oracle_standalone/adump/*")

Metrics extraction

Log processing rule

Configure the log processing rule to extract log attributes from the log content:

Metric extraction

Extract metrics from log entries to enable alerting:

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.

FAQ

Troubleshooting

Explore in Dynatrace Hub

Collect Oracle Database metrics and audit logs to monitor performance and security.