AppDynamics for Databases
2.9.x Documentation
The AppDynamics for Databases Agent can be configured to collect CPU consumption metrics from the monitored host.
Note: In order to enable OS Monitoring you must have selected the “Monitor OS?” checkbox and entered details of OS Type and hostname (or ipaddress).
AppDynamics for Databases can monitor Linux or Solaris from any of its supported platforms.
To collect OS metrics from Linux or Solaris the AppDynamics for Databases Agent will make an ssh connection to the monitored host and gather information using standard commands. For the AppDynamics for Databases Agent to monitor successfully the monitored host must support ssh connections, and the AppDynamics for Databases Agent must have a hostname, username and password defined.
AppDynamics for Databases can only monitor Windows from a Windows platform.
The AppDynamics for Databases Agent 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 Agent needs to be an authenticated user, therefore either the username and password should be defined explicitly in the OS Monitor settings, or the AppDynamics for Databases Agent windows service can be modified to run as an authenticated user, in the same way as outlined below.
1. When creating the agent in the Agent Manager, do not specify a username and password.
2. Configure the agent windows service to log on as the desired windows account with SQL Server access.
a. Go to the Windows Services UI from Control Panel. Select the AppDynamics for Databases Agent Service and right click to display the properties.
b. Click *Log On
* and then enter the credentials for the user.
c. Click *OK*, and then try starting the agent either from the services panel or from the Agent Manager.
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 your AppDynamics for Databases software on Linux then you must use SQL Server authentication.