To monitor Microsoft Azure with Database Visibility, you must run Microsoft Azure >= 2008. 

To configure an Azure SQL Managed Instance, follow the configuration procedures of a Microsoft SQL Server Collector. See Configure Microsoft SQL Server Collectors.

Procedures in this page are specific to an Azure SQL Database collector and not applicable for an Azure SQL Managed Instance. 

Connection Details

Create New CollectorDatabase TypeThe database type that you want to monitor.
AgentThe Database Agent that manages the collector.
Collector NameThe name you want to identify the collector by.
Connection DetailsHostname or IP AddressThe hostname or IP address of the machine that your database is running on.
DatabaseThe name of the database instance that you want to monitor.
Listener PortThe TCP/IP address of the port on which your database communicates with the Database Agent
Custom JDBC Connection StringThe JDBC connection string generated by the database agent. You can also specify a custom connection string, which is useful for setting custom authentication options.
Username and PasswordUsernameThe name of the user who is connecting to and monitoring the database through the Database Agent. The user should have the permissions described in User Permissions for Microsoft Azure.
PasswordThe password of the user who is connecting to and monitoring the database through the Database Agent.
CyberArkClick to enable CyberArk for database username and password. When CyberArk is enabled, information about Application, Safe, Folder, and Object is required to fetch the username and password for your database. To use CyberArk with Database Visibility, you must download the JavaPasswordSDK.jar file from the CyberArk web site and rename the file to cyberark-sdk-9.5.jar. Then, you must copy the JAR file to the lib directory of the database agent zip file. 
Advanced OptionsSub-Collectors

Click to monitor multiple database instances in a consolidated view, and aggregate metrics of multiple databases. To monitor a custom cluster, you can add additional hostname or IP address, and port details for each sub-collector. You can add up to a total of 29 sub-collectors. Thereby, 30 databases can be monitored in a custom cluster. In addition to the licenses consumed by the main collector, each sub-collector consumes one or more licenses, depending on the database type.


  • All connection parameters other than the hostname or IP address, and port details of the sub-collector are the same as the main collector. If you want to specify different parameters for the sub–collectors, while creating or editing the collector configuration, you can do that only via the Create Collector API.

  • You cannot convert a custom cluster collector to a standalone collector. If you want to monitor a standalone database, delete the entire custom cluster collector and create a fresh standalone collector. However, note that deleting the custom cluster collector will delete all its historical data.
Connection PropertiesClick to add a new JDBC connection property or edit an existing property for relational databases.

User Permissions for Microsoft Azure

The user account used for monitoring can be an SQL Server authenticated account (if AppDynamics Database Visibility is running on Windows or Linux). 

Minimum Permissions Required for SQL Server Logon 

You can create an SQL Server authenticated login or user with minimal level of permissions. To create a SQL Server login, you must be connected to the primary database from an admin account through SQL Server Management Studio (SSMS) or SQL Editor.

The read-only access to the master database is required for the user account to monitor the database.

  1. Run the command given below to create a login. Specify a secure password in the command.

    CREATE LOGIN DBMon_Agent_User WITH PASSWORD = 'Password123'
  2. Run the following command in your Azure SQL database to create a user account for the newly created login:

  3. While connected to your Azure SQL database, run the command given below to grant the pre-requisite roles and privileges:

    grant VIEW DATABASE STATE to DBMon_Agent_User