Extend the platform,
empower your team.
Observe, analyze and optimize the usage, health and performance of your database
ExtensionDynatrace automatically detects all applications and microservices deployed in your system and how your system uses Oracle Database.
Dynatrace diagnoses anomalies in real time with AI and pinpoints the root cause in slow-performing or erroneous SQL statements. Deep code-level insights combined with cloud-native database server monitoring help you ensure a robust production environment.
The Oracle Database extension complements the client-side database usage insights by providing server-side observability starting with availability and performance statistics, down to individual SQL statements and log insights.
Get started for Oracle Database clients:
If the application that connects to the Oracle Database server runs on a virtual machine or bare-metal, install OneAgent on it to get started.
If the application that connects to the Oracle Database server runs as a workload in Kubernetes or OpenShift, set up Dynatrace on Kubernetes or OpenShift.
Activate the following OneAgent features to get full tracing insight:
Get started with Oracle Database servers:
If your Oracle Database server runs on a virtual machine or bare-metal, install OneAgent on it to get started with system performance metrics.
Activate the remote Oracle Database extension to get full insight into the Oracle Database server's health and performance combined with metrics and events.
The extension collects data by directly querying the database's performance views and thus requires a connection to the database. A dedicated user account is recommended for monitoring. For convenience, user creation scripts can be found here. These scripts will create a user with the CREATE_SESSION
role and SELECT
permissions on the following performance views:
CDB_DATA_FILES
CDB_TABLESPACE_USAGE_METRICS
CDB_TABLESPACES
CDB_TEMP_FILES
GV_$ARCHIVE_DEST
GV_$ARCHIVE_DEST_STATUS
V_$ASM_DISK_STAT
V_$ASM_DISKGROUP_STAT
V_$BACKUP_SET_DETAILS
GV_$CLUSTER_INTERCONNECTS
GV_$CONTAINERS
V_$CONTAINERS
GV_$CON_SYS_TIME_MODEL
GV_$CON_SYSSTAT
GV_$DATABASE
V_$DATABASE
V_$DATABASE_BLOCK_CORRUPTION
GV_$DATAFILE
V_$DATAFILE
GV_$DATAGUARD_STATUS
GV_$INSTANCE
GV_$INSTANCE_PING
GV_$LIBRARYCACHE
V_$LOG
GV_$METRIC
GV_$METRICGROUP
GV_$PARAMETER
GV_$PDBS
GV_$PGASTAT
V_$RECOVER_FILE
V_$RECOVERY_FILE_DEST
GV_$RESOURCE_LIMIT
V_$RMAN_BACKUP_JOB_DETAILS
GV_$SESSION
V_$SESSION
GV_$SGASTAT
GV_$SQL
V_$SQL
GV_$SQLAREA
V_$SQL_PLAN
V_$SQL_PLAN_STATISTICS_ALL
GV_$SYSSTAT
GV_$SYSTEM_EVENT
GV_$SYSTEM_WAIT_CLASS
V_$TABLESPACE
V_$TEMPFILE
Alternatively, the SELECT_CATALOG_ROLE
can be assigned to the monitoring user.
While the extension supports connecting directly to a Pluggable Database (PDB), our recommended approach to monitor a multitenant Oracle DB setup is to point to extension the CDB. PDB discovery and monitoring will occur automatically. In this case, explicit permissions to access data across all containers may be needed:
alter user <your_username> set container_data=all container = current;
These privileges are already included in the user creation scripts.
Users of the Databases App who want to make use of Query Execution Plans, will also need to provide permission for the V$SQL_PLAN
, V$SESSION
, V$SQL_PLAN_STATISTICS_ALL
and V$SQL
views. These permissions are included in the user creation scripts. See the execution plan monitoring section below for more details.
Finally, activate log monitoring to get full log insight.
Note:
With the TopN feature set, the extension reports the most time consuming queries on the Oracle Instance entity page, in a card called "Logs". Enabling this feature may expose sensitive data in the reported queries.
The following Oracle versions are supported:
The following architectures are supported:
SELECT name, value FROM v$parameter WHERE name = 'audit_trail';
OS
means that the audit logs are stored locally in the file.
SELECT value FROM v$parameter WHERE name = 'audit_file_dest';
specifies the log file's location
Configure LogAgent's security rules to allow access to local files, by adding the oracle.json
file under :
/var/lib/dynatrace/oneagent/agent/config/logmodule
%PROGRAMDATA%\dynatrace\oneagent\agent\config\logmodule
{
"@version": "1.0.0",
"allowed-log-paths-configuration": [
{
"directory-pattern": "/u01/app/oracle/admin/oracle_standalone/adump/",
"file-pattern": "*.aud",
"action": "INCLUDE"
}
]
}
Agent restart is not required, this config will be applied within 1 minute.
Use the log file location fetched via the query executed in the first step, e.g. /u01/app/oracle/admin/oracle_standalone/adump/*
.
An example configuration that includes only ORA-01017
that reports invalid username or password logon attempts could be configured using:
Log content is any of: (.*)RETURNCODE:\[(\d+)\] "1017 AND Log source is any of: /u01/app/oracle/admin/oracle_standalone/adump/*
Logs collected the way described above can be accessed using following DQL query:
fetch logs | filter matchesValue(log.source, "/u01/app/oracle/admin/oracle_standalone/adump/*")
.
Configure log processing rule to extract log attributes out of the log content:
matchesValue(log.source, "/u01/app/oracle/admin/oracle_standalone/adump/*")
PARSE(content, "
DATA ' RETURNCODE:['INT']' SPACE '\"' INT:ora.returncode LD") |
PARSE(content, "
DATA ' USERID:['INT']'SPACE CSVDQS:ora.userid LD") |
PARSE(content, "
DATA ' USERHOST:['INT']'SPACE CSVDQS:ora.userhost LD")
Extract metrics from log entries to enable alerting:
log.oracle.invalid_credentials
matchesValue(log.source, "/u01/app/oracle/admin/oracle_standalone/adump/*")
Occurence of logs records
For SaaS customers with access to the Databases app, the execution plan monitoring functionality is also available when analyzing statement performance.
For this feature to work, the DBMS_XPLAN
package needs to be available, and the user configured in the Dynatrace extension needs to have permissions to call the DISPLAY_CURSOR
function. As per the official documentation this means that SELECT
or READ
permissions are required on the following views:
V$SQL_PLAN
V$SESSION
V$SQL_PLAN_STATISTICS_ALL
V$SQL
In addition to this, the SELECT
permission is also required for V$SQL_PLAN
.
Please note that the execution plan monitoring feature may sometimes not work as expected for RAC deployments. This will be fixed as soon as possible.
Query performance tracking may expose sensitive data in reported statements. Consequently, Dynatrace provides an optional mechanism that allows masking selected attributes. Details are available in the official documentation.
The configurations below present and example of how the sensitive data can be masked within the statements tracked.
Settings -> Log Monitoring -> Processing
USING(INOUT content) | FIELDS_ADD(content: REPLACE_PATTERN(content, "(\"'\"):p1 (LD):p2 (\"'\"):p3", "${p1}${p2|sha1}${p3}"))
logProcessingRules:
- ruleName: TopN statements masking
query: event.group="query_performance"
enabled: true
ProcessorDefinition:
rule: |
USING(INOUT content) | FIELDS_ADD(content: REPLACE_PATTERN(content, "(\"'\"):p1 (LD):p2 (\"'\"):p3", "${p1}${p2|sha1}${p3}"))
RuleTesting:
sampleLog: |
{
"event.group": "query_performance",
"content": "/*dt:ownQuery*/SELECT DECODE(name, 'sessions', value) AS sessions_limit, DECODE(name, 'processes', value) AS processes_limit FROM v$parameter WHERE name IN('sessions', 'processes')"
}
Please adjust this rule to match your use case.
The metrics collected through this extension consume Dynatrace Davis Data Units (see DDUs for metrics).
A rough estimation of the amount of DDUs consumed by metric ingest can be obtained through the following formula:
(55 * number of instances * 525.6) + (7 * number of databases * 525.6) + (8 * number of backup jobs per year * 0.005) + (5 * number of ASM disks * 525.6) + (3 * number of ASM disk groups * 525.6)
For logs, regular DDU consumption for log monitoring applies. Depending on your licensing model, refer either to DDU consumption for Log Management and Analytics or DDUs for Log Monitoring Classic.
This extension will run from your Dynatrace ActiveGates and connect to the configured databases. Once the connection has been established, the extension will regularly run queries on the database to gather performance and health metrics, reporting the results back to Dynatrace.
Only SELECT
queries are executed to collect data, and the vast majority of these will be selecting GV$
or V$
views. To see exactly which queries are executed, please download the extension yaml
artifact by going to Release notes, opening a release and pressing the Download version
button.
From version 3.2.0
onwards, query execution frequency is controlled by the configuration variables query-interval
and heavy-query-interval
. Most of the queries executed by the extension will run every query-interval
minutes (with a default of 1 minute), while the queries under tablespaces
and tablespaces (detailed)
, Blocked sessions
and TopN
will run every heavy-query-interval
minutes (with a default of 5 minutes).
For older versions, most queries run every minute, with exceptions for the heavy queries mentioned above, which run every 5 minutes.
Feature set
and Feature set (detailed)
The following feature sets have both a regular version and a detailed versions. These can be enabled or disabled in accordance to your specific use-case:
asm
and asm (detailed)
asm
feature set captures only ASM disk group data, while the asm (detailed)
feature set captures data for all disks. Both feature sets can be enabled at the same time.waitEvents
and waitEvents (detailed)
waitEvents
feature set will collect wait time metrics aggregated by wait class, while the waitEvents (detailed)
feature set collects metrics for the top 20 wait events.tablespaces
and tablespaces (detailed)
tablespaces
feature set does not collect the com.dynatrace.extension.sql-oracle.tablespaces.allocatedSpace
metric coming from CDB_DATA_FILES
(which tablespaces (detailed)
does). Furthermore, the tablespaces
feature set only collects data for tablespaces with more than 50% used space (as reported by CDB_TABLESPACE_USAGE_METRICS
), while the tablespaces (detailed)
feature set collects metrics for all tablespaces. Only one of these feature sets should be enabled at any given time.For some of the Dataguard metrics, not seeing any data is the correct behavior and it means the Data guard deployment is working as expected. The following metrics will only show datapoints in case there are issues which need further investigation:
Below is a complete list of the feature sets provided in this version. To ensure a good fit for your needs, individual feature sets can be activated and deactivated by your administrator during configuration.
Metric name | Metric key | Description | Unit |
---|---|---|---|
Cluster topology | com.dynatrace.extension.sql-oracle.cluster_topology | A state metric whose dimensions represent all Oracle clusters and their linked instances and hosts | NotApplicable |
Database topology | com.dynatrace.extension.sql-oracle.database_topology | A state metric whose dimensions represent all Oracle instances and their linked databases | NotApplicable |
Instance status | com.dynatrace.extension.sql-oracle.status | A state metric representing the details of the connected Oracle instance. | State |
Database status | com.dynatrace.extension.sql-oracle.db_status | A state metric representing details of the connected Oracle database. | State |
Metric name | Metric key | Description | Unit |
---|---|---|---|
FRA Usage | com.dynatrace.extension.sql-oracle.fra.usage | The percentage disk utilization in the fast recovery area. | Percent |
FRA limit | com.dynatrace.extension.sql-oracle.fra.limit | Maximum amount of disk space (in bytes) that the database can use for the fast recovery area. This is the value specified in the DB_RECOVERY_FILE_DEST_SIZE initialization parameter. | Byte |
FRA used | com.dynatrace.extension.sql-oracle.fra.used | Amount of disk space (in bytes) used by fast recovery area files created in current and all previous fast recovery areas. Changing fast recovery areas does not reset SPACE_USED to 0. | Byte |
FRA reclaimable | com.dynatrace.extension.sql-oracle.fra.reclaimable | Total amount of disk space (in bytes) that can be created by deleting obsolete, redundant, and other low priority files from the fast recovery area | Byte |
Metric name | Metric key | Description | Unit |
---|---|---|---|
Number of wait events by wait class | com.dynatrace.extension.sql-oracle.wait.count | Total number of waits by wait class, excluding 'Idle' events | Count |
Seconds waited by wait class | com.dynatrace.extension.sql-oracle.wait.time.count | Total amount of time waited by wait class, excluding 'Idle' events | MicroSecond |
Metric name | Metric key | Description | Unit |
---|---|---|---|
Datafile status | com.dynatrace.extension.sql-oracle.datafile.status | State metric representing the status of Datafiles and Tempfiles across containers (database and any PDBs). | NotApplicable |
Datafile number of corrupted blocks | com.dynatrace.extension.sql-oracle.datafile.corrupted_blocks | Metric representing the number of corrupted blocks reported by V$DATABASE_BLOCK_CORRUPTION for each Datafile | Count |
Metric name | Metric key | Description | Unit |
---|---|---|---|
Physical bytes read | com.dynatrace.extension.sql-oracle.io.bytesRead.count | Total size in bytes of disk reads by all database instance activity including application reads, backup, recovery, and other utilities | Byte |
Physical bytes written | com.dynatrace.extension.sql-oracle.io.bytesWritten.count | Total size in bytes of all disk writes for the database instance including application activity, backup, recovery, and other utilities | Byte |
Total wait time | com.dynatrace.extension.sql-oracle.io.wait.count | Total time spent in all wait states except for Idle class | MilliSecond |
Metric name | Metric key | Description | Unit |
---|---|---|---|
CPU cores | com.dynatrace.extension.sql-oracle.cpu.cores | Number of CPU cores | Count |
Background CPU usage (per second) | com.dynatrace.extension.sql-oracle.cpu.backgroundTotal | CPU usage of background processes in centi seconds per second | Unspecified |
Foreground CPU usage (per second) | com.dynatrace.extension.sql-oracle.cpu.foregroundTotal | CPU usage of foreground processes in centi seconds per second | Unspecified |
Metric name | Metric key | Description | Unit |
---|---|---|---|
PGA aggregate limit | com.dynatrace.extension.sql-oracle.memory.pga.size.pgaAggregateLimit | Limit on the aggregate PGA memory consumed by the instance | Byte |
PGA aggregate target | com.dynatrace.extension.sql-oracle.memory.pga.size.pgaAggregateTarget | Target aggregate PGA memory available to all server processes attached to the instance | Byte |
PGA memory used | com.dynatrace.extension.sql-oracle.memory.pga.used | PGA memory consumed by work areas | Byte |
Allocated PGA | com.dynatrace.extension.sql-oracle.memory.pga.allocated | Current amount of PGA memory allocated by the instance | Byte |
Shared pool free | com.dynatrace.extension.sql-oracle.memory.sga.cacheBuffer.sharedPoolFree | Amount of free system global area (SGA) memory available in shared pool | Percent |
Redo log space wait time | com.dynatrace.extension.sql-oracle.memory.sga.redoBuffer.redoLogSpaceWaitTime.count | Total elapsed time of waiting for redo log space request | MilliSecond |
Redo size increase | com.dynatrace.extension.sql-oracle.memory.sga.redoBuffer.redoSizeIncrease.count | Total amount of redo generated in bytes | Byte |
Redo write time | com.dynatrace.extension.sql-oracle.memory.sga.redoBuffer.redoWriteTime.count | Total elapsed time of the write from the redo log buffer to the current redo log file | MilliSecond |
Logical reads | com.dynatrace.extension.sql-oracle.memory.sessionLogicalReads.count | The sum of "db block gets" plus "consistent gets" | Count |
Physical reads | com.dynatrace.extension.sql-oracle.memory.physicalReads.count | Total number of data blocks read from disk | Count |
Physical reads direct | com.dynatrace.extension.sql-oracle.memory.physicalReadsDirect.count | Number of reads directly from disk, bypassing the buffer cache | Count |
Sorts in memory | com.dynatrace.extension.sql-oracle.memory.memorySorts.count | Number of sort operations that were performed completely in memory and did not require any disk writes | Count |
Sorts on disk | com.dynatrace.extension.sql-oracle.memory.diskSorts.count | Number of sort operations that required at least one disk write | Count |
Library cache hit ratio | com.dynatrace.extension.sql-oracle.memory.libraryCacheHitRatio | Library cache hit ratio | Percent |
Metric name | Metric key | Description | Unit |
---|---|---|---|
Total size | com.dynatrace.extension.sql-oracle.tablespaces.totalSpace | Total size of tablespace, including extensibility. This covers both allocated an unallocated space as large as the tablespace can expand. | Byte |
Free space | com.dynatrace.extension.sql-oracle.tablespaces.freeSpace | Total free space available in the tablespace, in bytes. This includes space that is currently allocated and available for reuse and space that is currently unallocated. | Byte |
Used space | com.dynatrace.extension.sql-oracle.tablespaces.usedSpace | Total space in use within the tablespace, in bytes. | Byte |
Tablespace usage | com.dynatrace.extension.sql-oracle.tablespaces.usage | The percentage of tablespace in use, relative to the total size (including extensibility). | Percent |
Metric name | Metric key | Description | Unit |
---|---|---|---|
Free space | com.dynatrace.extension.sql-oracle.asm.disk_group.free_mb | Free disk space available on this Oracle ASM Disk Group | MegaByte |
Total space | com.dynatrace.extension.sql-oracle.asm.disk_group.total_mb | Total disk space available on this Oracle ASM Disk Group | MegaByte |
Used space | com.dynatrace.extension.sql-oracle.asm.disk_group.usage | Percentage of disk space used on this Oracle ASM Disk Group | Percent |
Metric name | Metric key | Description | Unit |
---|---|---|---|
Free space | com.dynatrace.extension.sql-oracle.asm.disk.free_mb | Free disk space available on this Oracle ASM Disk | MegaByte |
Total space | com.dynatrace.extension.sql-oracle.asm.disk.total_mb | Total disk space available on this Oracle ASM Disk | MegaByte |
Used space | com.dynatrace.extension.sql-oracle.asm.disk.usage | Percentage of disk space used on this Oracle ASM Disk | Percent |
Reads | com.dynatrace.extension.sql-oracle.asm.disk.reads.count | Number of reads from this Oracle ASM Disk | Count |
Writes | com.dynatrace.extension.sql-oracle.asm.disk.writes.count | Number of writes to this Oracle ASM Disk | Count |
Metric name | Metric key | Description | Unit |
---|---|---|---|
Connection management time | com.dynatrace.extension.sql-oracle.queries.connectionManagement.count | Time spent on performing session connect and disconnect calls | MicroSecond |
PL SQL exec time | com.dynatrace.extension.sql-oracle.queries.plSqlExec.count | Time spent on running the PL/SQL interpreter | MicroSecond |
SQL exec time | com.dynatrace.extension.sql-oracle.queries.sqlExec.count | Time spent on executing SQL | MicroSecond |
SQL parse time | com.dynatrace.extension.sql-oracle.queries.sqlParse.count | Time spent on parsing SQL | MicroSecond |
DB Time | com.dynatrace.extension.sql-oracle.queries.dbTime.count | Time spent on performing Database user-level calls | MicroSecond |
DB CPU | com.dynatrace.extension.sql-oracle.queries.cpuTime.count | CPU time spent on performing database user-level calls | MicroSecond |
Metric name | Metric key | Description | Unit |
---|---|---|---|
Instance ping | com.dynatrace.extension.sql-oracle.rac.instance_ping | Represents the current inter-instance ping of 8K messages as provided in GV$INSTANCE_PING. | MicroSecond |
- | com.dynatrace.extension.sql-oracle.rac.interconnects | - | - |
Metric name | Metric key | Description | Unit |
---|---|---|---|
Total size | com.dynatrace.extension.sql-oracle.tablespaces.totalSpace | Total size of tablespace, including extensibility. This covers both allocated an unallocated space as large as the tablespace can expand. | Byte |
Free space | com.dynatrace.extension.sql-oracle.tablespaces.freeSpace | Total free space available in the tablespace, in bytes. This includes space that is currently allocated and available for reuse and space that is currently unallocated. | Byte |
Used space | com.dynatrace.extension.sql-oracle.tablespaces.usedSpace | Total space in use within the tablespace, in bytes. | Byte |
Allocated space | com.dynatrace.extension.sql-oracle.tablespaces.allocatedSpace | Total space in use within the tablespace, in bytes. | Byte |
Tablespace usage | com.dynatrace.extension.sql-oracle.tablespaces.usage | The percentage of tablespace in use, relative to the total size (including extensibility). | Percent |
Metric name | Metric key | Description | Unit |
---|---|---|---|
Active Sessions | com.dynatrace.extension.sql-oracle.sessions.active | Active sessions count | Count |
Blocked Sessions | com.dynatrace.extension.sql-oracle.sessions.blocked | Blocked sessions count | Count |
Total sessions | com.dynatrace.extension.sql-oracle.sessions.all | Total sessions count | Count |
User calls | com.dynatrace.extension.sql-oracle.sessions.userCalls.count | Total number of logins, parses, or execute calls | Count |
Deadlocks | com.dynatrace.extension.sql-oracle.sessions.deadlocks.count | Total number deadlocks | Count |
Metric name | Metric key | Description | Unit |
---|---|---|---|
Total size | com.dynatrace.extension.sql-oracle.pdb-total_size | Shows the disk space (in bytes) used by the PDB, including both data and temp files. | Byte |
Block size | com.dynatrace.extension.sql-oracle.pdb-block_size | The current block size for the PDB | Byte |
Diagnostic size | com.dynatrace.extension.sql-oracle.pdb-diagnostic_size | Shows the current disk space usage (in bytes) of the diagnostic traces generated in the PDB. | Byte |
Audit files size | com.dynatrace.extension.sql-oracle.pdb-audit_files_size | Shows the current disk space usage (in bytes) by Unified Audit files (.bin format) in the current PDB. | Byte |
Max size | com.dynatrace.extension.sql-oracle.pdb-max_size | Shows the maximum amount of disk space (in bytes) that can be used by data and temp files in the PDB. If the value is 0 then there is no limit. | Byte |
Max diagnostic size | com.dynatrace.extension.sql-oracle.pdb-max_diagnostic_size | Shows the maximum amount of disk space (in bytes) that can be used by diagnostic traces generated in the PDB. If the value is 0 then there is no limit. | Byte |
Max audit size | com.dynatrace.extension.sql-oracle.pdb-max_audit_size | Shows the maximum amount of disk space (in bytes) that can be used by Unified Audit files (.bin format) in the PDB. If the value is 0 then there is no limit. | Byte |
Metric name | Metric key | Description | Unit |
---|---|---|---|
Dataguard severe events | com.dynatrace.extension.sql-oracle.dataguard.severeEvents | Counts the number of fatal and severe Data guard events occurred in the last day. If this count is greater than 0, check its dimensions to take action for the specific events. | Count |
NOLOGGING activity | com.dynatrace.extension.sql-oracle.dataguard.nologgingActivity | Counts the number of files which contain NOLOGGING activity in the last day. If the count is greater than 0 then the standby database is vulnerable; check the dimensions to find out which files must be refreshed on the standby. | Count |
Archive destination status | com.dynatrace.extension.sql-oracle.dataguard.archiveDestErrStatus | Counts the number of invalid or errored statuses of archive destinations. If the count is greater than 0, use the dimensions to understand the status and destination it refers to. | Count |
Seq. difference | com.dynatrace.extension.sql-oracle.dataguard.seqDifference | Tracks the difference in sequence number between the latest archived and applied redo log. Use this count along with the dimensions to identify gaps between the primary and archive destination. | Count |
Metric name | Metric key | Description | Unit |
---|---|---|---|
Sessions utilization | com.dynatrace.extension.sql-oracle.limits.sessions_utilization | Utilization of sessions on the instance. This is a percentage of current utilization relative to the limit. | Percent |
Processes utilization | com.dynatrace.extension.sql-oracle.limits.processes_utilization | Utilization of processes on the instance. This is a percentage of current utilization relative to the limit. | Percent |
Metric name | Metric key | Description | Unit |
---|---|---|---|
Number of wait events | com.dynatrace.extension.sql-oracle.wait.events.count | Total number of waits by wait event, excluding 'Idle' events. Only collects the top 20 most time consuming events. | Count |
Seconds waited | com.dynatrace.extension.sql-oracle.wait.events.time.count | Total amount of time waited by wait event, excluding 'Idle' events. Only collects the top 20 most time consuming events. | MicroSecond |
Metric name | Metric key | Description | Unit |
---|---|---|---|
Input bytes | com.dynatrace.extension.sql-oracle.backup-input_bytes | Sum of all input file sizes backed up. | Byte |
Output bytes | com.dynatrace.extension.sql-oracle.backup-output_bytes | Output size of all pieces generated. | Byte |
Elapsed seconds | com.dynatrace.extension.sql-oracle.backup-elapsed_seconds | Number of elapsed seconds. | Second |
Compression ratio | com.dynatrace.extension.sql-oracle.backup-compression_ratio | Compression ratio. | Percent |
Input bytes per second | com.dynatrace.extension.sql-oracle.backup-input_bytes_per_second | Input read-rate-per-second. | BytePerSecond |
Output bytes per second | com.dynatrace.extension.sql-oracle.backup-output_bytes_per_second | Output write-rate-per-second. | BytePerSecond |
Auto - backup count | com.dynatrace.extension.sql-oracle.backup-autobackup_count_number | Number of autobackups performed by this job. | Count |
Backup state | com.dynatrace.extension.sql-oracle.backup.state | A state metric representing the details of a Backup Job. | State |
Time since last backup | com.dynatrace.extension.sql-oracle.backup.time_since | The time elapsed since the last backup completed successfully. | Minute |
query-interval
and heavy-query-interval
to control the extension's monitoring queries' execution frequency.Tablespaces (detailed)
in order to better control the extension's resource consumption on the database. The current query for tablespaces monitoring has been moved to Tablespaces (detailed)
and the the Tablespaces
feature set now contains a simpler, less resource-intensive query to monitor tablespaces. This query drops the com.dynatrace.extension.sql-oracle.tablespaces.allocatedSpace
metric and only monitors tablespaces with more than 50% used space.
Tablespaces (detailed)
feature set will be disabled by default. To continue collecting tablespace metrics as before enable this new feature set in existing configurations and disable the Tablespaces
feature set. ⚠️sql-oracle_database
entity.ℹ️ This version requires ActiveGate version 1.301.0 or higher.
SAME_AS
relationship not being established properly.ℹ️ This version requires ActiveGate version 1.293.0 or higher.
ℹ️ This version requires ActiveGate version 1.293.0 or higher.
asm (detailed)
introduced in order to better control license consumption for ASM disks. ASM disk metrics are moved to this new feature set, while ASM disk group metrics remain in the asm
feature set.
asm (detailed)
feature set will be disabled by default. To continue collecting ASM disk metrics enable this new feature set in existing configurations. ⚠️ℹ️ This version requires ActiveGate version 1.293.0 or higher.
sql:com_dynatrace_extension_sql-oracle_host
, was dropped and its data is now shown on the Oracle Instance screen.runsOn
to calls
.dt.entity.host
, now have a sameAs
relationship with instances.SQLAREA
. This will also change the value of the log.sql-oracle.top_n_queries.
metrics.sql:com_dynatrace_extension_sql-oracle_cluster
, was added and will be active whenever a RAC setup is detected.CDB$ROOT
is now detected as a container. Tablespaces and datafile charts for the CDB$ROOT
are now show in the CDB$ROOT
's database screen as opposed to in the instance screen.ℹ️ This version requires ActiveGate version 1.293.0 or higher.
sessions
feature setBlocked sessions
feature set.
Records can be filtered by event.group == "blocked_sessions"
in the log query.TopN
feature set
endpoint_metadata
attribute of the Oracle Instance entity and
can be used in entity selectors (to facilitate tagging, for example).event
dimension from com.dynatrace.extension.sql-oracle.wait.count
and com.dynatrace.extension.sql-oracle.wait.time.count
to prevent inadvertently high DDU consumption. To replace the previous functionality a new feature set, waitEvents (detailed)
, was added with metrics com.dynatrace.extension.sql-oracle.wait.events.count
and com.dynatrace.extension.sql-oracle.wait.events.time.count
which report total waits and total wait time for the top 20 wait events. When updating monitoring configs to the new version, make sure you enable the new feature set if you want to continue getting event level details.CDB_TABLESPACE_USAGE_METRICS
which takes into account the underlying filesystem (same as Oracle Enterprise Manager)Due to the topology changes mentioned below, your environment may create new entities to replace the ones created by older versions of the extension.
Any custom configuration relying on the following entity types will not work:
sql:com_dynatrace_extension_sql-oracle_cdb
sql:com_dynatrace_extension_sql-oracle_pdb
(replace with sql:com_dynatrace_extension_sql-oracle_database
)sql:com_dynatrace_extension_sql-oracle_service
Instance status
metric and entity propertiesRenaming the dashboard and updating the tags
Recyclebin is taken into account for free space calculation in tablespaces.
Fixed incorrect definition of Oracle host entity related to most time consuming queries.
Add a primary dimension definition to the extension alerts
Fixed Management Zone filtering on Oracle Database extensions dashboard.
Initial extension release