Splunk AppDynamics collects metrics for database calls and response times at the following levels:

• Business transaction metrics: The metrics for a specific business transaction for a specific database are visible on the transaction flow map.
• Tier metrics: The metrics for all calls from a tier to the specified database are visible on the tier flow map.
• Database call metrics: The overall database access metrics across the application (all business transactions) are visible on the application flow map and the Database Calls dashboard.
• Integrated database metrics withDatabase Visibility:
  • When a database Collector has been set up in Splunk AppDynamics Database Visibility, you can link to that product from the Application and Database Calls dashboards. If you have already associated the database server with a Database Collector in Database Visibility, you can view the Database Visibility UI. If not, the disconnected database icon is displayed and you are prompted to link the database to an already configured server or cluster in Database Visibility. Also, you must have view permission to the corresponding collector configured in Database Visibility, to map/un-map it with the database server or cluster.

    

  • A relational database backend of a Java application has the same hostname, port number, and database type as a database server already configured in a database Collector. The Oracle backend is automatically matched with the correspondingDatabase VisibilityCollector. The Snapshot correlation view, which is available for relational database backends, shows the details of queries, clients, sessions, and schemas when the snapshot was captured.

    

  • When a backend database is linked to a server or a cluster in Database Visibility, clicking the database icon displays basic details with a link to Database VisibilityUI. You can also view the database KPI metrics.

    

By default, many databases and data stores are automatically detected when calls are made from nodes instrumented with Splunk AppDynamics app agents. See Access Database Visibility from Application Monitoring Views.

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:

Database Icon	Status
	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 inDatabase Visibility. Click the database icon, then theConnectlink to link the database backend to the appropriate server or cluster.