Working with monitoring profiles

Set up monitoring profiles to tailor how Db2 Query Monitor monitors specific workloads.

Monitoring profiles control various aspects of monitoring such as summary reporting, SQLCODE reporting, exception limits, alert notifications thresholds, collection of host variable information, and OPTKEYS override settings. Monitoring profiles do not affect Db2 command reporting.

Monitoring profiles are optional and can be changed for a monitoring agent while the monitoring agent is still collecting information.

Monitoring profiles enable you to fine-tune the inclusion and exclusion of specific workloads from query monitoring and thereby determine the type of activity that is to be collected by Db2 Query Monitor. A monitoring profile consists of a set of include/exclude monitoring profile lines that Db2 Query Monitor reads sequentially as it looks for a match. The order in which monitoring profile lines are placed is important as it determines the order in which Db2 Query Monitor looks for a match and, if found, includes or excludes activity information.

Db2 Query Monitor reads the list of profile lines from top to bottom. When a match is found, the activity is processed according to the parameters specified in the matching monitoring profile line and no additional monitoring profile lines in the monitoring profile are considered for that activity.

You can configure monitoring profile to:

  • Disable summary reporting for specific workloads
  • Include or exclude SQLCODE reporting for specific workloads
  • Set exception limits and thresholds
  • Define exception and alert thresholds for particular SQL workloads
  • Define whether or not to gather host variable information
  • Activate the current activity display for particular SQL workloads
  • Exclude particular SQL workloads from summary data collection
  • Override the OPTKEYS settings for the summary data collection for a specific SQL workload
Note: Monitoring profiles do not have any effect on Db2 command reporting.