The Agent for database monitoring runs directly on / is part of the Dynatrace Collector, so no additional component needs to be installed. It connects to a database instance using a JDBC connection string.
When configuring a Database Agent you will need to select the Collector on which it will be started.
As mentioned on the Database Monitoring main page it is important also for configuration to differentiate between
- the DB monitoring on the DBMS instance level, overarching a whole Dynatrace installation described here on one hand and
- the JDBC, ADO.Net and PHP DB sensors on the System Profile / app level that capture SQL statements (and bind values) and their count and timing,... and come with the Java, .Net and PHP Agents respectively on the other hand.
See also Database Agent Troubleshooting in case of issues.
Grant Necessary Permissions for DB Monitoring
The user that is used to connect to the DB instance needs to be granted the following permissions:
|Database Platform||Permissions needed|
CREATE SESSION, SELECT_CATALOG_ROLE
|MS SQL Server|
VIEW ANY DATABASE, VIEW SERVER STATE
Refer to the release notes for more details about supported versions.
SQL Server 2012 & 2014
Oracle Database 11g/12c
Database monitoring is configured Dynatrace-installation-globally in Settings menu > Dynatrace Server... > Databases > Create or Edit. (Conversely the JDBC, ADO.Net and PHP DB sensors are configured in the tiers > Sensor Configuration of a System Profile.)
Initially DB Agents can be added from the Application Environment Configuration wizard > <any app type in step 1> > Configure Databases – or later directly from the context menu of an automatically detected database tier in the Transaction Flow.
In any case: Configuring DB monitoring (Agents) you will end up in the Settings menu > Dynatrace Server... > Databases > Create dialog.
In any other case you will be handed on to the Add Tier wizard, always accessible in the Cockpit sidebar > System Profile context menu.