Setting up historical monitoring

Historical monitoring data is stored in a repository database. You will need to activate repository persistence and set associated values in your monitoring profile to ensure IBM® Data Server Manager (DSM) presents the data you need.

To set up monitoring of historical data for your database connection:

1. Go to Settings > Monitoring Profiles.
2. From the All Monitoring Profiles page, expand the vendor that matches your database (e.g., Db2) select your monitoring profile and then click Edit.
3. Click Persistence and set it to ON.
4. From the Settings panel, ensure that SQL statement execution data is selected.
   This tells DSM to collect historical data about executed SQL statements and store it in the repository database.
5. Expand SQL statement execution data and select Package cache data (Top N).
   This tells DSM to collect historical data from the Db2® package cache and store it in the repository database.
6. Accept the default values or set ones that reflect your own business needs, for the following properties:
   • Collect and persist data every X minutes: indicates the number of minutes between historical SQL monitoring cycles (default value is 5 minutes)
   • Number of SQL statements with the highest values for a metric to capture: indicates the 'N' value used to capture the 'Top N most interesting' SQL statements for each metric.
   • Keep data for X days: indicates the number of days that DSM will keep the data in the repository database before removing it.
   • Normalize captured SQL statements: when selected, this feature replaces literal values entered dynamically into captured SQL statements with question mark (?) symbols, to reduce the potentially infinite number of SQL statements down to a manageable amount.
7. Click Save.
   
   Historical information about executed SQL statements can now be collected by DSM for the connected database.