Oracle Database monitoring configuration
After you define the scope of your configuration, you need to identify the network devices you'd like to collect data from and identify the ActiveGates that will execute the extension and connect to your devices.
Make sure that all the ActiveGates from the ActiveGate group you'll define as the scope can connect to a respective data source. You can assign an ActiveGate to a group during installation by using the --set-group-name
installation parameter or by configuring your ActiveGate.
The monitoring configuration is a JSON payload defining the connection details, credentials, and feature sets that you want to monitor. For details, see Start monitoring.
Example payload to activate an Oracle SQL extension:
[
{
"value": {
"enabled": true,
"description": "My Oracle SQL extension",
"version": "0.1.1",
"featureSets": [
"io",
"cpu",
],
"sqlOracleRemote": {
"licenseAccepted": true,
"endpoints": [
{
"host": "sqlserver.org",
"port": 1521,
"databaseIdentifier": "serviceName",
"authentication": {
"scheme": "basic",
"username": "admin",
"password": "password"
},
"serviceName": "some-serviceName"
}
]
}
},
"scope": "ag_group-default"
}
]
When you have your initial extension YAML ready, package it, sign it, and upload it to your Dynatrace environment. For details, see Manage extension lifecyle.
The Dynatrace Hub-based extension activation wizard contains a dynamically updated JSON payload with your monitoring configuration
You can also use the Dynatrace API to download the schema for your extension that will help you create the JSON payload for your monitoring configuration.
Use the GET an extension schema endpoint.
Issue the following request:
curl -X GET "{env-id}.live.dynatrace.com/api/v2/extensions/{extension-name}/{extension-version}/schema" \
-H "accept: application/json; charset=utf-8" \
-H "Authorization: Api-Token {api-token}"
Make sure to replace {extension-name}
and {extension-version}
with values from your extension YAML file. A successful call returns the JSON schema.
Scope
Note that each ActiveGate host running your extension needs the root certificate to verify the authenticity of your extension. For more information, see Sign extension.
The scope is an ActiveGate group that will execute the extension. Only one ActiveGate from the group will run this monitoring configuration. If you plan to use a single ActiveGate, assign it to a dedicated group. You can assign an ActiveGate to a group during installation with the --set-group-name
installation parameter for Linux and Windows, or by configuring your ActiveGate.
Use the following format when defining the ActiveGate group:
"scope": "ag_group-<ActiveGate-group-name>",
Replace <ActiveGate-group-name>
with the actual name.
Version
Version of this monitoring configuration. Note that a single extension can run multiple monitoring configurations.
Description
Human-readable description of the specifics of this monitoring configuration.
Enabled
If set to true
, the configuration is active and Dynatrace starts monitoring immediately.
Endpoints
You can define up to 100 endpoints in a single monitoring configuration in the SQLOracleRemote
section.
"sqlOracleRemote": {
"licenseAccepted": true,
"endpoints": [
{
"host": "sqlserver.org",
"port": 1521,
"databaseIdentifier": "serviceName",
"authentication": {
"scheme": "basic",
"username": "admin",
"password": "password"
},
"serviceName": "some-serviceName"
}
]
}
}
Oracle JDBC Driver
The Oracle SQL data source requires the Oracle JDBC driver distributed by Dynatrace. By setting the licenceAccepted
property to true
, you indicate that you have read and accepted the Dynatrace redistribution license agreement for Oracle JDBC Driver.
To define an Oracle Database server, add the following details in the endpoints
section:
- Host
- Port
- Database identifier, either
serviceName
orsid
. - Authentication credentials
Authentication
Authentication details passed to the Dynatrace API when activating monitoring configuration are obfuscated and it's impossible to retrieve them.
Feature sets
Add a list of feature sets you want to monitor. To report all feature sets, add all
.
"featureSets": [
"cpu",
"io"
]