Database monitoring

Database monitoring provides DB instance level views: (a) the database instance dashlet represents the current database state and load level broadly, by graphing request frequency, CPU and HDD usage, wait state distribution and others. (b) the database live view presents a point in time snapshot of the database activity, presenting database sessions, database activity types (in the form of wait states), currently running big/slow queries and others (c) AppMon 2018 April If enabled on a given agent ("Enable top SQLs and wait states analytics"), the WebUI DB views have been extended with Slow Queries and Wait state views. These present the top most work intensive queries and database activity types (wait states) in a given time slice, starting with 5 minute granularity and decreasing with passing time.
PurePath based views relating to databases have been integrated with DB agent functionality allowing for (a) easy db agent configuration from the transaction flow dashlet (b) viewing explain plans for queries retrieved from PurePaths or viewed in the slow queries dashlets. For AppMon 2017 May and later, database monitoring is available for Oracle Database (including Oracle RAC), Microsoft SQL Server, MySQL, Aurora and IBM DB2.

This complements the fully integrated, application-related capturing of connection pool usage, SQL statements and transaction response time contribution available for every DB call using JDBC, ADO.NET and PHP DB sensors in Java, .NET and PHP Agents respectively.

Data for any monitored database appearing in a PurePath automatically maps into the System Profile, when a PurePath mapped to a profile calls a database.

Database Agent

The Database Agent directly runs on the AppMon Collector and as such is delivered out-of-the-box and no other components are needed. It connects to a database instance and retrieves data every 30 seconds (measures) or on-demand (live view, execution plan).

Database Agent configuration

Configuration consists of two parts—configure connection settings on the AppMon side, and grant necessary permissions for the Agent user on database side. See Database Agent configuration to learn more.

Click Settings > Dynatrace Server > Databases to reach the configuration dialog box. See Database configuration if you need instructions.

Auto-mapping of Database Agents into System Profiles

To merge global DB-monitoring data with application-specific data such as SQL statements, database agents dynamically map into the System Profiles if a database tier is detected on a PurePath and that same database instance is monitored. This mapping can be checked in the Status Overview dashlet of a specific System Profile.

A database mapping into a specific System Profile is a prerequisite for viewing database monitoring data in the WebUI, as WebUI views are always filtered by the selected System Profile.

Access database monitoring data

Access dashboards from the Monitoring Overview breadcrumbs or by a drill-down from a specific database node in the Transaction Flow.

Monitored database instances overview

The list of all monitored database instances is available in the Database Instances dashlet. To access it:

  • AppMon 2017 May In the Cockpit, double-click Databases node.
  • AppMon 2018 April In the Server section of the sidebar, click Databases.

Drill down from Transaction Flow to Database Monitoring dashboards

There are several drill-downs from a database-related Transaction Flow node to specific dashboards, such as Database Health.


The following permissions in AppMon control access to database monitoring:

  • Show Database Monitoring
  • Manage Database Monitoring

It is necessary to have them to be able to change the Database Agents configuration.