AppDynamics for Databases

2.9.x Documentation

Skip to end of metadata
Go to start of metadata

On this page:

AppDynamics for Databases can be configured to collect CPU consumption metrics from the monitored host. Host monitoring is not supported for the Microsoft SQL Azure Database platform.

AppDynamics for Databases supports Windows, Linux, and Solaris and gathers granular data on server performance, which displays on the following Server tabs:

  • Inventory tab: Server properties such as CPU architecture and speed, Physical Memory, OS version etc.
  • Procs tab: Remotely view processes on your monitored servers
  • Activity tab: CPU and memory consumption, and disk queue length
  • Disk I/O tab: Read IOPS, Write IOPS, Read Throughput MB/sec, Write Throughput MB/sec, Average Disk Queue Length 
  • Network I/O tab:  kB/sec Sent and Received, TCP send/receive errors

To see server metrics, in the Monitored Infrastructure section of the Main Menu, click Server.

Note: To enable the Host Collector for database servers only, on the Add Collector or Edit Collector Configuration pages you must click the Monitor OS? checkbox and enter details of OS Type and Hostname (or IP address.)

Monitor Linux, Solaris, and AIX Servers

AppDynamics for Databases can monitor Linux, Solaris, and AIX systems from any of its supported platforms.

To collect OS metrics from Linux or Solaris, the AppDynamics for Databases Host Collector makes an ssh connection to the monitored host to gather information using standard commands. For the AppDynamics for Databases collector to successfully collect information, the monitored host must support ssh connections, and the AppDynamics for Databases Host Collector must have a hostname, username and password defined.

Monitor Windows Servers

AppDynamics for Databases can only monitor Windows from a Windows platform.

The AppDynamics for Databases Host Collector will collect OS metrics from a Windows host via Windows Management Instrumentation (WMI). To collect OS metrics from a remote Windows machine, the AppDynamics for Databases Host Collector must be an authenticated user; therefore, either the username and password should be defined explicitly in the OS Monitor settings, or the AppDynamics for Databases Windows service should be modified to run as an authenticated user, in the same way as outlined in Using Windows Authentication to Monitor SQL Server.

Configure Windows Authentication to Monitor SQL Server

  1. When creating a collector on the Collector Setup page, do not specify a username and password.
  2. Configure the AppDynamics for Databases windows service to log on as the desired windows account with SQL Server access.
    1. Go to the Windows Services UI from Control Panel. Select the AppDynamics for Databases collector service and right click to display the properties.
    2. Click Log On and then enter the credentials for the user.
    3. Click OK, and then try starting the collector either from the services panel or from the Collector Administration page
  3. Repeat the above process for the AppDynamics for Databases GUI Windows Services.

The AppDynamics for Databases GUI windows service also needs to be configured to log on as the desired windows account with SQL Server access; this is because to display some windows within AppDynamics for Databases, such as the Current window and the Objects window, the UI process needs to make a direct connection to the monitored SQL Server to request information.

If you are running AppDynamics for Databases on Linux then you must use SQL Server authentication.

Required NetApp Permissions

For complete AppDynamics for Databases functionality in a NetApp environment, the NetApp Metric Collector needs access NetApp API access. Depending on your environment, clustered or non-clustered, see the following topics:

AppDynamics for Databases can use either HTTP or HTTPS (i.e. SSL) to access the performance data. If your filer uses SSL, then just check the SSL checkbox on the Add New Collector or Edit Collector Configuration page.

See also Map NetApp Volumes to Databases.

NetApp OnTap 7mode Permissions

Here is an example user creation script if you would like to create a new dedicated user for AppDynamics for Databases with relevant privileges:

useradmin role add Appd4db_Role -a api-perf-*,api-system-get-info,api-system-get-version,api-aggr-list-info,api-volume-list-info,api-disk-list-info,api-snapmirror-get-status,login-http-admin
useradmin group add Appd4db_Group -r Appd4db_Role
useradmin user add appd4db -g Appd4db_Group

Required NetApp Clustered Data OnTap Permissions

 Here is an example user creation script if you would like to create a new dedicated user for AppDynamics for Databases with relevant privileges:

security login create -username appd4db -application ontapi -authmethod password -role readonly