Manage Oracle Database extensions
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. Oracle Database extensions support:
- Oracle standalone servers
- Oracle Multitenant (CDB/PDB)
- Oracle Database versions 12c-21c
- 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 used for monitoring and grant him the following roles:
SELECT_CATALOG_ROLEyou can also grant this user a
SELECTpermission on following performance views:
Manage Oracle SQL extensions
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
- From the Dynatrace menu, go to Dynatrace Hub.
- Search for an Oracle Database extension. You can use the Oracle SQL keyword to filter the Hub tiles.
- Select Add to environment. This creates the environment configuration for your extension, thus enabling the extension in your environment.
- Select Add monitoring configuration.
After that, perform the following steps.
Accept Oracle JDBC driver redistribution license
An Oracle Database extension requires that you accept the Dynatrace redistribution license agreement for Oracle JDBC Driver.
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:
- 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
Select the ActiveGate group to determine which ActiveGates will run the extension. When done, select Next step.
Provide final configuration details.
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.