Dynatrace provides you with a framework that you can use to extend your application observability into data acquired directly from your Oracle Database layer, so that you can monitor how database server tasks impact your app.
To get started, check Dynatrace Hub to see if the Dynatrace-provided Oracle Database extension satisfies your requirements. If this is not the case, you can build your own Dynatrace Oracle Database extension.
Before you begin
Decide which Oracle Database server you want to monitor. The Oracle Database extension supports Oracle Database versions 12.2+ with the following setups:
Oracle standalone servers
Oracle Multitenant (CDB/PDB)
Oracle RAC
Oracle AWS RDS
Designate an ActiveGate group or groups that will remotely connect to your Oracle Database server to pull data. All ActiveGates in each designated group need to be able to connect to your Oracle Database server.
Create a dedicated user account for monitoring and grant it permissions as in the Oracle Database extension description under the Get started with Oracle Database servers section.
Manage Oracle SQL extensions
Extension Manager
Latest Dynatrace
Now you can use the dedicated Extensions app to manage your extensions. It provides a similar activation and configuration workflow as Dynatrace Hub in the previous Dynatrace. Additionally, it gives you direct access to extension health monitoring.
To use the app:
In Dynatrace Hub , select and install the app.
The Hub listing provides information on the permissions required to use the app (the Technical information tab).
Dynatrace Hub provides a unified workflow to enable and manage extensions that will ingest Oracle Database data into your Dynatrace environment.
Required permission: Change monitoring settings
In Dynatrace Hub, select and install the Oracle Database extension. (You can use "Oracle SQL" to filter search results.) This enables the extension in your environment.
Add a monitoring configuration so that the extension can begin collecting data.
Select Add Oracle endpoint to define the Oracle Database servers from which you want to pull data. You can define up to 100 endpoints. Provide the following connection details:
Host
Port
Database identifier, either Service Name or SID.
Authentication credentials. Note that only basic authentication is supported. Authentication details passed to Dynatrace when activating monitoring configuration are obfuscated and it's impossible to retrieve them.
You can use credential vault to provide a more secure approach of storing and managing user credentials.
When done, select Next step
ActiveGate group
Select the ActiveGate group to determine which ActiveGates will run the extension. When done, select Next step.
Activate extension
Provide final configuration details.
Description
Text explaining details of this particular monitoring configuration. When troubleshooting monitoring, this can give your teams details of this particular monitoring configuration.
Feature sets
In highly segmented networks, feature sets can reflect the segments of your environment. You can use them to limit your monitoring to particular segments. Feature sets are predefined for each extension.
When done, select Activate.
Monitoring configuration as JSON
The extension activation wizard contains a dynamically updated JSON payload with your monitoring configuration. See Extensions 2.0 lifecycle to learn how to use it to activate an extension using the Dynatrace API.