Global - operations

Operation-related global settings enable you to define options that apply to all monitored operations. These settings take precedence over the options defined for individual operations.

NAM Console ► Deployment ► Manage devices, NAM Probe Configuration ► Open configuration, select Configuration ► Global ► Operations to display the general configuration settings.

The options are:

Operation load time threshold

The number of seconds after which an operation is considered “slow”. You can set this value with a precision of one ten-thousandth of a second.

Default: 0.5000 seconds.

The threshold is used by following analyzers:

  • IBM over MQ
  • Jolt
  • MS Exchange
  • Oracle Forms over HTTP
  • Oracle Forms over HTTPS
  • Oracle Forms over SSL
  • Oracle Forms over TCP
  • SOAP over HTTP
  • SOAP over HTTPS
  • XML
  • XML over HTTP
  • XML over HTTPS
  • XML over MQ
  • XML over SSL

Max. operation duration

The maximum number of seconds an operation can take. You can set this value with a precision of one ten-thousandth of a second.

Default: 3600 seconds (1 hour).

User abort threshold

The minimum number of seconds between the beginning of a hit and TCP reset to count it as a user abort.

Default: 1.6000 seconds. (You can set this value with a precision of one ten-thousandth of a second.)

ADS data generation settings

The options in the ADS data generation settings section can be used to handle various types of standalone hits, which are hits that cannot be automatically assigned to operations because the reference information, such as correlating response, defined or auto-learned URL, no authorization, or orphaned redirects, is missing. By default, most standalone hits are not taken into account when generating operations data.

Report data without monitored URL

Select this option to report data for hits without a URL that has been explicitly defined in user-defined services or recorded through auto-learning.

Report standalone hits without monitored URL

Select this option to report data for standalone hits that at the same time do not refer to a monitored URL, as in Report data without monitored URL. Standalone hits are hits without a response header, unauthorized hits, orphaned redirects, or other hits missing the reference context.

Report hits without response header

Select this option to report data for discarded hits (hits without a correlating response header).

Report hits not added to any operation

Select this option to report data for other standalone hits caused by factors not covered by other options of this section.

Report unauthorized hits

Select this option to report data for hits with rejected authentication.

Report orphaned redirects

Select this option to report data for redirects to sites that are not being monitored or are not visible and therefore appear as orphaned redirects.

Report filtered data

This is a diagnostics option. When configuring content type monitoring, you can filter out pages based on the content of the URL. For more information, see Content Type Monitoring. If you select this option, the filtered out pages are not reported, but are saved in the NAM Probe data files.

Ignored clients

A list of clients for which TCP setup time are ignored and all operations start from the request packet. Right-click the list to open a menu of command options: Add, Edit, or Delete.