You can monitor any version of Sybase IQ with Database Visibility.
|Create New Collector||Database Type||The database type that you want to monitor.|
|Agent||The Database Agent that manages the collector.|
|Collector Name||The name you want to identify the collector by.|
|Connection Details||Hostname or IP Address||The hostname or IP address of the machine that your database is running on.|
|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, for example, |
|Username and Password||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 Sybase IQ.|
|Password||The password of the user who is connecting to and monitoring the database through the Database Agent.|
|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 |
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.|
|Exclude Databases||The databases that you want to exclude, separated by commas.|
|Monitor Operating System||See Configure the Database Agent to Monitor Server Hardware.|
User Permissions for Sybase IQ
To monitor with a non-DBA account, you need:
- User account with SERVER OPERATOR system privilege.
Execution privileges on several procedures which can be granted as follows:
grant execute on sp_iqconnection to DBMon_Agent_User grant execute on sp_iqtransaction to DBMon_Agent_User grant execute on sp_iqcontext to DBMon_Agent_User grant execute on sp_iqstatus to DBMon_Agent_User grant execute on sp_iqcolumn to DBMon_Agent_User grant execute on sp_iqindex to DBMon_Agent_UserCODE
DBMon_Agent_Useris the user name under which you run the Database Visibility Agent.
Grant DBA authority to
grant DBA to DBMon_Agent_UserCODE