How Db2 instrumentation data matches exception thresholds
During exception processing, Db2 instrumentation data records are tested against matching threshold conditions in the Exception Threshold data set.
When a record matches more than one threshold, the best matching threshold is chosen of those detecting an exception.
The key fields of a record are:
- Location
- Group
- Subsystem ID
- Member
- Requesting Location
- Connection
- Plan Name
- Correlation Name
- Correlation Number
- Primary Authorization ID
These key fields are compared with the corresponding fields in the thresholds and the threshold that best matches the record is chosen. This is done by comparing the Location of the record with the Location field of the matching thresholds first. A key field that does not contain an asterisk is considered a better match than one that contains asterisks. If two thresholds are found to match the record equally, the Group fields are compared with the record. If these fields also match the record equally, the Subsystem ID fields are compared with the record, and so on for the following fields:
- Member
- Requesting Location
- Connection
- Plan Name
- Correlation Name
- Correlation Number
- Primary Authorization ID
Exception checking in the reporting phase is performed on entries that are constructed according to your ORDER specification, which contains up to three OMEGAMON for Db2 PE identifiers. For example, if you qualify a field by PLANNAME and CONNECT, exception checking on the field is performed only if you specified both PLANNAME and CONNECT in ORDER.
Package-related fields are supported on a “by total” and “by thread” basis only.