Other protocols monitoring - universal decode

In the Universal Decode section you set parameters specific to monitoring Universal Decode-based software services.

The Universal Decode was formerly known as the Simple Parser.

General

Universal Decode global settings are provided as part of Other Protocols Monitoring configuration. These global settings can be overridden by specific settings for a particular software service.

To configure Universal Decode global settings:

  1. Open the General settings for the Universal Decode analyzer. To access global general settings for Universal Decode, in NAM Console ► Deployment ► Manage devices, NAM Probe Configuration ► Open configuration, go to Global ► Other Protocols Monitoring ► Universal Decode ► General in the navigation tree.
  2. Optional: Configure the maximum request and response sizes for the Universal Decode analyzer. This is an advanced setting. Its purpose is to protect the NAM Probe from badly formulated Universal Decode scripts or from erroneous traffic which would overload the parser. Do not alter this setting unless you have been advised to do so by the provider of the particular Universal Decode script you are going to use. The maximum request and response sizes defined here relate to the particular protocol being analyzed by the Universal Decode. The analyzed protocol can be thought of as stacked above the TCP layer, with TCP being used as its transport layer. Therefore, a single request or response in this context, can consist of many TCP packets.

Auto Learning

Operation auto-learning enables you to define the set of operations identified by the Universal Decode without the need to manually define each operation.

Operations that are found frequently are learned and reported.

  • Open the Auto learning settings for the Universal Decode analyzer To access global auto learning settings for Universal Decode, in NAM Console ► Deployment ► Manage devices, NAM Probe Configuration ► Open configuration, go to Global ► Other Protocols Monitoring ► Universal DecodeAuto learning in the navigation tree.
  • Select the Enable auto-learning check box to enable auto-learning for all services based on the Universal Decode analyzer.
  • Specify the size of reported operations pool. If necessary, you can change the default size of reported operations pool. The pool is shared among all monitored servers. The auto-learning algorithm aggregates the operations for all servers - the server IP, port or any other attribute of the server is not taken into account by the auto-learning algorithm. Any member of the pool will be reported for all servers, regardless the activity on individual servers.
  • Enter the number of reported elements. You can specify the maximum number of different operations that will be reported and learned.
  • Configure advanced auto-learning settings Click Advanced settings to show the properties so you can adjust the behavior of the auto-learning algorithm. The design behavior of the auto-learning algorithm for the Universal Decode analyzer are directly analogous to those for the auto-learning of URLs and you can adjust these settings accordingly.

Availability

You can configure Universal Decode availability globally or at the software service level, overriding the global settings.

For global configuration, open NAM Console ► Deployment ► Manage devices, NAM Probe Configuration ► Open configuration, and go to Global ► Other Protocols Monitoring ► Universal Decode ► Availability. For the software service level, select the Availability tab in the Edit Rule window.

In Universal Decode availability reporting, for each failure category, you can control the error classification by using the following options available in the list next to each of the available transport and application errors:

Enabled

Error is classified as failure.

Disabled

Error is not classified as a failure.

Failures (transport)

Incomplete responses

You can determine whether the following types of incomplete responses should be classified as failures (transport).

Partial response (standalone hit)

An incomplete response observed for a hit without an operation context, classified as a Dead hit. This pertains to situations when server started the response but never finished due to a timeout or other problems.

Aborted response (standalone hit)

An incomplete response observed for a hit without an operation context, classified as a Break. This pertains to situations when server started the response but aborted it before completion with TCP reset.

No response

A request hit with no response from a server. This pertains to situations when server did not respond at all or responded in unrecognizable way.

Partial response

An incomplete response with a Dead hit status. This pertains to situations when server started the response but never finished due to a timeout or other problems.

Aborted response

An incomplete response with a Break status. This pertains to situations when server started the response but aborted it before completion with the TCP reset.

Universal Decode transport errors

The NAM Probe is able to deliver information on the transport errors classified into seven categories.

You can decide whether each of these should be taken into account when calculating (failures transport). Note that Universal Decode client errors (4xx), Universal Decode server errors (5xx), Universal Decode unauthorized errors, Universal Decode Not Found errors, and Universal Decode server errors (category 1) have configurable contents. For more information, see Web - Errors.

Failures (application)

Universal Decode is capable of detecting the application fatal error and error indicators. On top of that, you can also decide whether operation attributes 3 to 5 should be reported as failures (application).

Fault Domain Isolation

Use the following threshold settings to accurately identify the true source of the problem:

Server time threshold
The Server time threshold relates to the server time portion of an overall operation time. Server times above the threshold limit are considered to be slow due to poor datacenter performance.

Idle time threshold
Threshold for the time during the operation execution when there is no network or server activity related to the operation. It is assumed that Idle time is caused by the user's software not sending requests because user's PC is busy.

Network time threshold
Threshold for the time the network (between the user and the server) takes to deliver requests to the server and to deliver page information back to the user. In other words, Network time is the portion of transaction time that is due to the delivery time on the network.

Retransmissions threshold
Percentage of retransmissions regarding all observed transmissions.

Network time affected by high retransmission threshold
Percentage of the network time affected by high retransmission threshold.

Request size threshold Threshold for the request where anything larger would be considered big request.

Network time affected by the transfer of a big request threshold
Threshold for the request where anything larger would be considered big request.

Response size threshold
Threshold for the response where anything larger would be considered big response.

Network time affected by the transfer of a big response threshold
Threshold for the network time that is affected by the transfer of a big response threshold.

Number of hits threshold
Threshold for the number subcomponents of error-free operations or transactions.

Single hit duration threshold
Threshold for a hit duration as a percentage of operation time.

Rtt threshold
Threshold for the time it takes for a SYN packet to travel from the client to a monitored server and back again.