Dynatrace 6.3 Documentation

Other Doc Versions & KB

Skip to end of metadata
Go to start of metadata

Overview

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 PlatformPermissions needed
Oracle

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

Example script with the minimum permissions required for SQL Server 2012 & 2014

Oracle Database 11g/12c

Example script with the minimum permissions required for an Oracle Database

Configuration

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.


  • No labels
  1. Anonymous (login to see details)

    There's a broken link for the item below, on the side bar.

    Database Diagnostics Use Cases with Dynatrace

    1. Anonymous (login to see details)

      thanks Gabriel - I have just fixed it.

      1. Anonymous (login to see details)

        In troubleshooting section for database connection, the link for this page- permissions is broken. I had to search for it.

  2. Anonymous (login to see details)

    Hi, my costumer is asking me that if there is an overhead because of DB dynatrace Agent? why?

  3. Anonymous (login to see details)

    Hi,

    Is SELECT_CATALOG_ROLE role mandatory? can we monitor DB with just CREATE SESSION?

  4. Anonymous (login to see details)

    is there any other DB server supported except SQL SERVER and ORACLE?

    1. Anonymous (login to see details)

      Hi Ravneet, 

      Thanks for asking. The System Requirements lists supported database information. See the 6.3 System Requirements at https://community.dynatrace.com/community/display/DOCDT63/System+Requirements.

      Thanks

      Dave Bignotti

       

  5. Anonymous (login to see details)

    Hi David, 

    As per the section for DB Agents, it lists only Oracle and SQL Server.

    Dynatrace Agent

    • Supported agent Platforms and Operating Systems
    • Oracle (Sun) JVM, IBM JVM, JRockit JVM, HP JVM
    • 10MB disk space
    • DB Agent supports Oracle Database 11g/12c and Microsoft SQL Server 2012/2014 

    1. Anonymous (login to see details)

      Hi Ravneet, 

      Yes, those are the Supported databases in 6.3 version for the Agent.

      I saw that you commented on a forum request for Sybase support. If you haven't voted on that request, please do so (I also submitted a vote). The more votes, the higher research priority the request receives.

      Thanks,

      Dave Bignotti

      1. Anonymous (login to see details)

        Sure David, I will vote for it. Thanks for your help, appreciate that.