This page applies to an earlier version of the AppDynamics App IQ Platform.
See the latest version of the documentation.


Skip to end of metadata
Go to start of metadata

On this page:

Related pages:

Your Rating:
Results:
PatheticBadOKGoodOutstanding!
52 rates

Systems that AppDynamics Database Visibility Supports

Once Database Visibility is available, you can create collectors that run on the Database Agent to monitor any of the following systems:

System Category

System Type

Supported via Amazon RDS

Version

Databases

 

 

 

 MongoDB, MongoDB cluster 2.2 and higher
 

MySQL

yes

all versions including Percona and MariaDB

 

Microsoft SQL Serveryes

2005, 2008, 2012, 2014, 2016 and SQL Azure

 

Microsoft SQL Server on Linux

 SQL Server on Linux is currently available as a public preview, and is not recommended for production use. Database Visibility works correctly with this preview release, but until a stable version of SQL Server on Linux is available, monitoring results may vary.
 Oracle, Oracle RACyes10g, 11g, and 12c

 

PostgreSQL

yes

all versions

 IBM DB2 LUW 9.x, 10.x, 11.x

 

Sybase ASE

 

15+

 Sybase IQ  
    

Hardware Monitoring

 

 

 

 Windows 

32-bit (will also work on 64-bit systems)

 Linux 32-bit and 64-bit

 

Solaris

 

all versions

 

AIX

 

 

 Amazon RDS  

To avoid metric value errors, use a 64-bit JRE with the 64-bit operating system.

If you use a third-party application along with Database Visibility to monitor Sybase, the data displayed in the controller may not display correctly. For accurate metrics, it is recommended that you do not use both a third-party application and Database Visibility to monitor Sybase.


Agent Hardware Requirements

Hardware requirements vary depending on database activity. If your database activity increases, you may need to adjust your hardware configuration.

The machine running the Database Agent should meet following hardware requirements:

  • 1 GB of heap space and an additional 512 MB of heap space for each monitored database instance. For less busy databases, you can reduce the heap space to 256 MB per monitored database instance.
  • 2 GHz or higher CPU

Examples of heap space allocation:

  • Monitoring 5 databases instances requires ( 5 x 512 MB ) + 1024 MB = 3,584 MB
  • Monitoring 20 database instances requires ( 20 x 512 MB ) + 1024 MB = 11,264 MB
  • Monitoring 100 database instances requires ( 100 x 512  MB ) + 1024 MB = 52,224 MB

AppDynamics Controller Sizing Requirements

The controller database should meet the following hardware requirements:

  • 500 MB of disk space per collector per day
  • 500 MB of disk space for the Events Service per day. By default, the Events Service retains data for 10 days.

For information on additional hardware requirements for the AppDynamics Controller to support Database Visibility, see Controller System Requirements

Start the Controller Events Service

The Database Agent requires the Events Service, which must be started before starting the agent.

Software Requirements

  • The Database Agent runs on a Java Virtual Machine. You must have Java 1.7 or 1.8.
  • The operating systems Linux and Windows are supported

Network Requirements

  • The machine on which the database is running or the machine you want to monitor must be accessible from the machine where the Database Agent is installed and running. This machine must have a network connection, internet or intranet.
  • If your databases are behind a firewall, you must configure the firewall to permit the machine running the Database Agent program access to the databases. The database listener port (and optionally the SSH or WMI port) must be open.
  • The network bandwidth used between the agent and the controller is approximately 300kb/min per collector for a large database with 200 clients using 50 schemas, processing about 10,000 queries a minute. The actual numbers depend on the type of database server, the number of individual schemas on the server, and the number of unique queries executed daily, and will therefore vary.