Setting up monitoring profile
Historical monitoring data is stored in a repository database. You need to activate repository persistence and set associated values in your monitoring profile to ensure IBM® Db2® Data Management Console presents the data.
About this task
Go to Creating a repository data that you needbase for Db2 Data Management Console for detailed steps on how to create a repository database and the associated connection in IBM Db2 Data Management Console.
To set up monitoring of historical data for your database connection:
- Log in to IBM Db2 Data Management Console.
- Click Administration and select Monitoring
profile. The Monitoring profile page appears. To modify the settings for the existing profile, expand the vendor that matches your database (e.g. Db2), select your monitoring profile and then click Edit.
- To create a new profile, from the Monitoring profile page, click Create profile.
- From the General tab, enter the profile name and assign databases to this profile.
- Click the Monitor settings tab and enter the following details.
Collect data every (minutes)
Indicates the number of minutes between historical monitoring cycles. The default value is 5 minutes.
Package cache SQL statements captured
The top N SQL statements with the metrics of highest value that is gathered from the package cache, where N is the number of SQL statements captured.The following top 16 metrics are captured in the package cache:
Locks Lock wait threshold (milliseconds)
The amount of time spent in a lock waiting before an event is generated.
Table data read for a collection
The maximum number of table data that is read for a data collection.
Collect storage data
Collect storage data determines whether to capture the storage metric data for a monitored database.
For Db2 Data Management Console version 3.1.11 or earlier, selecting this option captures both table performance and table storage data for tables and indexes. If this option is cleared, both the table performance and table storage monitor KPIs are disabled.
As of Db2 Data Management Console version 3.1.12, selecting this option captures both table performance and table storage data for tables and indexes. If this option is cleared, only the table storage monitor KPI is disabled.Note: After you upgrade the console to version 3.1.12, the status of the table performance and table storage KPIs do not change. You need to explicitly select or deselect the Collect storage data option to change the status of the table performance and table storage monitor KPIs.
Storage data collection time (hh:mm)
Specifies the time of collection of storage data.
Storage compression caption
Capture estimated saving in kb/% by adaptive/static compression.
Normalize captured SQL statements
Selecting this option will replace the literal values with question mark (?) tokens to collapse the cardinality of unique SQL statements back to a (typically small) finite set.Note: This option is available in the following monitor pages:
Blocking and Waiting Connections
Locked Objects with Waiting Connections
Find Locked Objects
Lock Event Monitor
Persistence is off /on
Persistence toggle button
- Off - monitoring data will not be stored in the repository database.
- On - monitoring data about the selected settings will be stored in the repository database.
Selecting this option collects all the table function related historical information (excluding package cache) and store it in the repository database.Note: This option is available in the all the monitor pages except the package cache page and four event monitor related pages.
Selecting this option collects historical data from the Db2 package cache and store it in the repository database.
- Click the Alerts settings tab and edit the alert configuration.
- Click the Notification tab and specify the email and SNMP server settings.
- Click the Custom alerts tab and create or schedule custom alerts to run on specified databases.
- Click Save.
Historical information can now be collected by the Db2 Data Management Console for the connected database.