AppDynamics Oracle Database - Monitoring Extension

This extension works only with the standalone machine agent.

Use Case

The Oracle Database is an object-relational database management system.

The Oracle Database monitoring extension captures performance metrics from Oracle databases (version 10g and above) and displays them in AppDynamics. It retrieves metrics from the data dictionary and groups them in three categories:

• Activity: Throughput over the last minute, such as transactions, SQL executes, I/O reads and writes, average active sessions, etc.
• Resource Utilization: What database resources are currently in use (sessions, open cursors, shared pool, etc).
• Efficiency: Ratios and response times as indicators of the instance's efficiency.

Installation

1. The Oracle DB extension needs an Oracle user account on every Oracle instance that is to be monitored. You might use an existing account with appropriate rights; however, a dedicated account will be a better solution in terms of security and manageability.

• Example script for account creation (run this with a DBA user):

            CREATE USER appdynamics IDENTIFIED BY oracle;
            GRANT CREATE SESSION TO appdynamics;
            GRANT SELECT ANY DICTIONARY TO appdynamics;

2. Download and extract the OracleDBMonitor.zip into your <machine-agent-home>/monitors directory.

3. Configure the extension by editing the config.yml (See Configuration section below).

4. Restart the Machine Agent.

5. Look for the metrics in theAppDynamics Metric Browser under | Application Infrastructure Performance | <Tier> | Custom Metrics | Oracle Instance (SID).

Configuration

Note : Please make sure to not use tab (\t) while editing yaml files. You may want to validate the yaml file using a yaml validator

1. Configure the Oracle DB parameters by editing the config.yml file in <MACHINE_AGENT_HOME>/monitors/OracleDBMonitor/. Specify the host, port, username, password and sid of the Oracle DB instance.

   For eg.

       # Oracle DB connection params
       host: "localhost"
       port: 49161
       sid: "xe"
       username: "system"
       password: "oracle"
       # prefix used to show up metrics in AppDynamics
       metricPathPrefix:  "Custom Metrics|ORACLE Server|"
   
   

2. Configure the path to the config.yml file by editing the in the monitor.xml file in the <MACHINE_AGENT_HOME>/monitors/OracleDBMonitor/ directory. Below is the sample

    <task-arguments>
        <!-- config file-->
        <argument name="config-file" is-required="true" default-value="monitors/OracleDBMonitor/config.yml" />
         ....
    </task-arguments>
   

3. Download the oracle JDBC jar file and place it in the/monitors/OracleDBMonitor directory. Edit the monitor.xml and provide the name of the jar file in the classpath. For eg.

    
       oracle-monitoring-extension.jar;ojdbc6.jar
    

Metrics

Here is a summary of the collected metrics. Complete documentation of Oracle's metrics can be found at http://docs.oracle.com/cd/E11882_01/server.112/e17110/waitevents.htm#REFRN101.

AppDynamics displays metric values as integers. Some metrics are therefore scaled up by a factor of 100 for a better display of low values (e.g. between 0 and 2).

Metric class: Activity

Metric Class: Efficiency

Metric Class: Resource Utilization

Oracle Licensing

The metrics in the supplied code are retrieved from:

-   v$session
-   v$sesstat
-   v$sysmetric
-   v$system_wait_class
-   v$waitclassmetric

all of which are, to the best of our knowledge, not subject to additional licensing of the Oracle Diagnostics Pack. See Oracle's "Options and Packs" documentation: http://docs.oracle.com/cd/E11882_01/license.112/e10594/options.htm#CIHIHDDJ

Contributing

Always feel free to fork and contribute any changes directly via GitHub.

Community

Find out more in the AppSphere community.

Support

For any questions or feature request, please contact AppDynamics Center of Excellence.