Configure IBM DB2 Collectors

This page describes configuration details for IBM DB2 collectors.

Note: To monitor IBM DB2 with Database Visibility, you must be running DB2 >= 9.x.

Connection Details

SectionFieldDescription
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.
Note: If the database instance hosts multiple databases, ensure to create separate collector for each database.
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, for example, jdbc:db2://. You can also specify a custom connection string, which is useful for setting custom authentication options.

If you are using the connection string for Kerberos authentication, ensure to select the Kerberos option under Advanced Options.

Database Credentials UsernameThe 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 IBM DB2 LUW.
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.
HashiCorp VaultSee Configure the HashiCorp Vault.
Advanced OptionsSub-CollectorsClick 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.
Note:

  • 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 through 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.

For monitoring the database using Kerberos authentication, follow the instructions mentioned at Monitor IBM DB2 Databases Using Kerberos Authentication.

KerberosClick to use Kerberos authentication to manage the database user and host user passwords.
Monitor Operating SystemSee Configure the Database Agent to Monitor Server Hardware.