Use the Setup window to configure and administer your AppDynamics for Databases (AppD4DB) collectorsDatabases collectors.

The default Collector Administration window Administration window lists all configured collectors alphabetically. You can sort or filter the list using the controls above the table headings.

Add a License

Note: Please contact your AppDynamics account representative or AppDynamics Support for information on license usage and pricing.

1. On the Collector Administration window, click Add License.

2. On the Add/Edit License Key windowKey window, click Add License.

3. On the Add New License Key windowKey window, enter the license key and then click Add License.

    The new license appears on the License Management window which shows Management window which shows existing licenses and lets you add licenses.

    On the License Management windowthe License Management window, you can click Add Collector *to access the *Add New Collector window.

Add a Collector

Reconfigure a Collector

After adding a collector, you can change its attributes if needed. 

1. On the Collector Administration windowAdministration window, click the Stop button for the collector you want to reconfigure and then click its name.

...

Each collector has a Start/Stop button that starts or stops the collector service/process. The collector service/process has a name such as: DBTuna Agent - CollectorType.

• For Windows installations: The Start/Stop  button controls the Windows service associated with the collector.
• For Linux installations: The Start The Start/Stop  button controls the process associated with the collector.

...

To display the log file, click the Log icon in the table row. The log file, in reverse order from the end of the log. The most recent logs are at the beginning of the log file.

...

To refresh the log file contents, click Refresh. The Aggregation Interval you Interval you specified when configuring the collector, determines how often data is collected for the collector. There is one entry in the log file for every data collection. You may want to refresh the log file viewer if you have had the View Log File window open File window open for longer than the collection interval.

To return to the Collector Administration windowAdministration window, click All Collectors.

You can find the log files in <AppDynamicsInstallDir>\Controller\logs.

Manage the Archive

AppD4DB AppDynamics for Databases stores historical performance information in a local MySQL database installed and configured during AppD4DB AppDynamics for Databases installation. The Archive Management window displays the total space used by the MySQL database, broken down by tables and indexes.

...

The following describes the fields on the Archive Management windowManagement window.

Data Retention Period: Specify the number of days to retain the archive of historical performance information for all monitored instances. The maximum data retention period is 999 days. If required, you can backup the MySQL database for long term or off-site storage. The data used by AppD4DB AppDynamics for Databases for its own purposes is retained in  <installDir>\MySQL\MySQL Server 5.6\data\mysql.

Purge Interval: Click an entry in the list to specify how often you want to purge the archive, Every Day or Day or Every Hour.

Starting At: Using the 23 hr clock, click to specify the hour and minute when the purge activity should begin.

...

In larger monitored environments you can quickly access an individual database by displaying collectors grouped in the Host menu. For example, this NetApp environment belongs to the Dev group:

...

Depending on your environment, you may need to map your database to your NetApp volume in order to see database activity when you drill down from the NetApp volume into the NetApp Activity window in AppD4DBAppDynamics for Databases.

The following example shows the database information that is available for a monitored NetApp volume which holds an Oracle database.

...

For the Oracle via NFS to NetApp environment, the correlation between the NetApp volume and the database is done automatically, but for others you will need to define the mapping on the Mappings window. Using the Mappings window, you can map NetApp volumes to databases via protocols such as fibre channel protocol (FCP), internet Small Computer System Interface (iSCSI), and Common Internet File System (CIFS).

...