AppDynamics can monitor the performance of database calls made by instrumented applications, as described here.
AppDynamics collects metrics for database calls and response times at the following levels:
When a backend database is linked to a server or a cluster in Database Visibility, a click on the database icon displays basic details with a link to Database Visibility UI. You can also view the database KPI metrics.
To monitor call performance to a database, confirm that it appears in the Databases Calls list and has its own Database Calls dashboard. If a database is not appearing, check the configuration.
The database icons on the flow maps help you identify the status of the database. The following table lists the different database icons:
|The database is healthy. No active health rule violations|
|Health Rule Violation - Critical Condition|
|Health Rule Violation - Warning Condition|
|The database is either not linked to the appropriate server or cluster node. This icon also appears when the database is in the process of changing the state.|
The database is not connected to the server or cluster in Database Visibility.
Click the database icon, then the Connect link to link the database backend to the appropriate server or cluster.
Databases detected during the specified time window show up on the Application Dashboard flow map, where you can view them in the context of the entire application's transaction flow. The application flow map displays calls per minute and average response time for calls made to databases. These metrics include all calls made from a specific tier to a database across all business transactions. The tier and node flow maps display a similar metric aggregating data from calls across all business transactions by tier or node respectively.
The detected databases appear on the Tier Flow Map, where you can view them in the context of the traffic on this specific tier.
For business transactions involving calls to databases, the databases appear on the Transaction Flow Map, where you can view them in the context of the traffic for this specific business transaction. The transaction flow map shows the average time spent in database calls for the business transaction.
In addition to seeing monitored databases in the flow map, you can view the following information:
AppDynamics can sometimes reveal unexpected connections from an application to a database on the flow map. If this occurs for you, try the following to determine why this database appears:
The database list shows all detected databases along with key performance indicators. Stale databases can be configured to be automatically removed.
From the database list, you can select a database and click View to see the Database Calls dashboard. The dashboard displays a Database Flow Map, database properties, and Dynamic Baselines.. The database properties indicate how the agent identifies the database and control how it shows in the display map and how the metrics are aggregated. For a discussion of baselines and how they are used and configured, see
The database dashboard has two tabs and an action options menu:
The Action menu provides additional actions:
You can access the Database Server List by clicking Servers > Databases.
AppDynamics displays a list of the slowest database calls. For each call, you can view specific call details and related business transaction snapshots. The list shows up to ten database calls with the longest execution time over the selected time frame, by tier and for all tiers. Each call shows the following information:
App agents aggregate and report call data to the Controller every 15 minutes. Max Time determines which calls are displayed in the Slowest Database Calls list. For example for JDBC calls, Max Time must exceed 10 ms before AppDynamics tracks the call as a potential candidate for this list.
Slowest database calls are defines as:
To see slowest database calls, click Troubleshoot > Slow Response Times > Slowest DB and Remote Service Calls.
On this page, you can do the following:
AppDynamics displays NoSQL databases as Remote Services. See Remote Services.