On this page:
On this page:
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 topic are specific to an Azure SQL Database collector and not applicable for an Azure SQL Managed Instance.
|Database Type||The database type that you want to monitor.|
|Database Agent||The Database Agent that manages the collector.|
|Name||The name you want to identify the collector by.|
|Hostname or IP Address||The hostname or IP address of the machine that your database is running on.|
|Database||The name of the database instance that you want to monitor.|
|Failover Partner||The hostname or IP address of the failover partner.|
|Listener Port||The TCP/IP address of the port on which your database communicates with the Database Agent|
|Custom JDBC Connection String||The 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||The 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.|
|Password||The password of the user who is connecting to and monitoring the database through the Database Agent.|
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.
|Connection Properties||Click to add a new JDBC connection property or edit an existing property for relational databases.|
|CyberArk||Click 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.|
|Logging Enabled||Click to enable verbose mode logging, which logs all communications between the Controller and the Collector. Enable only during troubleshooting because logging consumes a lot of disk space. If you have enabled logging, you can click the logging icon in the Log column of the Collector Administration window to view the log file. The log files are located in the <db_agent_home>\agent directory and have the format <CollectorName>_out.log and <CollectorName>_err.log.|
User Permissions for Microsoft Azure
The user account used for monitoring can be a Windows authenticated account (if the Database Agent is running on Windows) or 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 a SQL Server authenticated login or user with minimal level of permissions. To create a SQL Server login, you must be connected to the master database from an admin account via SQL Server Management Studio (SSMS).
Run the command given below to create a login. Specify a secure password in the command.
Run the following command in your Azure SQL database to create a user account for the newly created login:
While connected to your Azure SQL database, run the command given below to grant the pre-requisite roles and privileges: