AppDynamics for Databases
For large scale deployments, or where monitored systems are extremely busy, please contact AppDynamics Support for installation recommendations and assistance.
On this page:
Once AppDynamics for Databases is up and running, you can create collectors that run on the AppDynamics for Databases server to monitor any of the following systems:
LUW 9.x, LUW 10.x
Microsoft SQL Server
2000 (Service Pack 3 and later), 2005, 2008, 2012, and 2014
|Microsoft SQL Azure Database|
all versions including Percona and MariaDB
|MongoDB||2.2 and higher|
8i, 9i, 10g, 11g, and 12c
IBM AIX Server
32-bit (will also work on 64-bit systems)
FAS 7 mode, Clustered Data ONTAP
NetApp E-Series Arrays
AppDynamics for Databases collectors are not installed on the monitored systems.
AppDynamics for Databases can be installed on physical or virtual machines.
You should install AppDynamics for Databases on a dedicated machine.
For information on hardware requirements of the AppDynamics Controller, see AppDynamics Pro, Controller System Requirements.
AppDynamics for Databases is an on-premise solution and can be installed on the same server as the AppDynamics Pro Controller, or on a different server. In either case it requires 1 CPU and 2GB of RAM to monitor a single database instance. If you install it on the Controller server, these resources are in addition to the Controller resources. Also, change the default port number so it doesn't conflict with the Controller.
For better navigation and performance, use Chrome or Safari.
Unknown User (firstname.lastname@example.org)
>If there is a firewall, the database listener port (and optionally the SSH or WMI port) must be open.
It would be nice to have examples. By "database listener port", for SQL Server I assume you mean 1433 (if i'm running standard). Would also be useful to understand what capabilities run over each port. I have restriction on WMI ports — no idea what I'm loosing here by not being able to open.