AppDynamics for Databases

2.9.x Documentation

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: replacing AppD4DB with AppDynamics for Databases

AppDynamics for Databases (AppD4DB) can Databases can be configured to collect CPU consumption metrics from the monitored host.

...

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

Collecting Information from Windows

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

The AppD4DB Host 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 AppD4DB Host 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 AppD4DB 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.

...

1. When creating a collector on the Collector Setup page, do not specify a username and password.

2. Configure the AppD4DB AppDynamics for Databases windows service to log on as the desired windows account with SQL Server access.

...