Configuring individual query monitoring

For analyzers such as TDS, DRDA, Informix, Oracle, and MySQL, use query monitoring to specify queries that are always reported regardless of their frequency or performance (regardless of whether they comply with query auto-learning requirements).

Skill level: advanced user

This screen offers functionality suitable for expert users.

  • If you are new to software services, start with Software services for beginners before you come here.
  • If you want to monitor a well-known software service, start with Autodiscovered Software Services to see if your work has already been done for you.
  • If you find you still need to define your own software service, try to use the wizard or a template to walk you through the process. You can always use the manual screens to tweak a software service after you create it with the wizard. See Software Services for details.


In NAM Console ► Deployment ► Manage devices, select NAM Probe Configuration ► Open configuration.

On the NAM Probe Configuration screen, select Software Services ► User-Defined Software Services.

On the User-Defined Software Services screen, select the software service for which you want to edit dimensions, metrics, or attributes.

For query monitoring, this should be a service using a relevant analyzer such as TDS, DRDA, Informix, Oracle, or MySQL.

Right-click in the Rules table to add or edit a rule.

On the Query Monitoring tab, right-click in the Key Queries table to open Configure Query.


In the Rule Configuration window, select Query Monitoring tab and add or edit the query in the Key Queries table to open Monitored Query dialog.

You can either specify a literally given query or use a regular expression that the query will match.

  • Exact
    Select Exact to add a literally given query. In such case, you have to provide a literal string for the query and its custom name.
  • Regular expression
    Select Regular expression to use a pattern to match a query. In such case you have to provide a regular expression to match a query and a custom name assigned to the matched occurrences. Note that when applying a regular expression, you can extract part of the query, getting rid of redundant elements. Optionally, you can specify the normalization method applied to queries found by means of regular expression.

Optionally, for both methods, you can override a default SQL query time threshold defined at the software service level. A query that takes more than this many seconds is considered slow. When Inherit setting from the rule is selected, the software service setting is used.

To report the key queries bypassing the auto-learning scheme, select always report query. If you already defined the key queries and temporarily wish to leave the decision on their monitoring to the query auto-learning scheme, clear always report query, which is a default setting. Note that the queries that bypass the auto-learning mechanism will not be displayed on reports showing queries which most frequently occur or the ones having longest execution time.

Configuration effects on reported data

Individual query monitoring settings affect data presentation on the NAM Server with regard to reporting hierarchy levels. Values that you enter in the Query definition section will be reported as operation names. They can be either combined or only the value from either field will be used. If set, Query name will be always visible on reports. If you use regular expressions to define individual queries they will also be reported as operation names. If you do not set the name then the value from Query field will be reported as operation name.