This data view provides dimensions and metrics to analyze the monitored traffic.

Software service, operation, and site data dimensions

Agent (id: applAgent)

The name of the synthetic agent that loaded the HTTP pages, for example, Keynote, Gomez, or Mercury. The name of the agent is determined from the User-agent field of the HTTP request and/or from agent user names or IP address configured on the server.

AMD-reported analyzer (id: primeCodec)

AMD-reported analyzer

Analysis type (id: analtyp)

It assumes two values: Non-transaction and Transaction. This is to determine if transactional (TCP-based) or non-transactional traffic will be considered.

Analyzer (id: anal)

The name of the traffic analyzer. For more information see Concept of Protocol Analyzers on Dynatrace Community.

Analyzer group (id: anlzGroup)

The logical group of analyzers based on the type of the analyzed traffic. For more information see Concept of Protocol Analyzers on Dynatrace Community.

Analyzer group (obsolete) (id: recType)

An analyzer group name. For example: Web, XML or Oracle Forms.

Analyzer group ID (id: recTypeID)

Analyzer group ID

Application (id: bgAppl)

A universal container that can accommodate transactions.

Application Monitoring Server ID (id: dtServerId)

Identifier of the Application Monitoring server.

Application Monitoring System Profile (id: dtSystemProfile)

Name of a used Application Monitoring System profile.

Business day (id: businessDay)

The classification of days as business or non-business, as defined in the Business Hours Configuration tool.

Business hour (id: businessHour)

The classification of hours, as business and non-business, as defined in the Business Hours Configuration tool. Possible values are Business and Off-business.

Call initiator (id: voipCallInit)

The IP address of the party initiating the call.

Call manager IP (id: voipCallMngIp)

The IP address of the call manager used in a VoIP call.

Citrix server (id: citrixServer)

The IP address of the Citrix server.

Class of service (id: clSer)

The name identifying a Type of Service value. The mapping of Class of Service names to different values of Type of Service is defined in Central Analysis Server configuration.

Client area (id: cLocArea)

Sites, areas, and regions define a logical grouping of clients and servers, or Backbobne nodes in case of Synthetic Backbone reports, into a hierarchy. They are based on manual definitions and/or on clients' BGP Autonomous System names, CIDR blocks or subnets. Sites are the smallest groupings of clients and servers. Areas are composed of sites. Regions are composed of areas.

Client city (id: cGeoCity)

Geographical data about the client site, or the Backbone node in case of Synthetic Backbone reports.

Client country (id: cGeoCountry)

Geographical data about the client country, or the Backbone node country in case of Synthetic Backbone reports.

Client geographical region (id: cGeoRegion)

Geographical data about the client region, or the Backbone node region in case of Synthetic Backbone reports..

Client group (id: userNGr)

The client's group, or a group of Backbone nodes in case of Synthetic Backbone reports, as manually defined in Central Analysis Server.

Client hardware (id: browsH)

The user's hardware type (for example, a mobile phone model).

Client identifier (id: cIdentifier)

Client identifier

Client identifier type (id: cIDType)

Client identifier type

Client internal IP address (id: cIntrIP)

Client IP address as seen in the client's local network.

Client IP address (id: cIP)

The IP address of the client, or the Backbone node in case of Internet synthetic reports.

Client name (id: clientN)

Client's name determined from HTTP cookie (requires configuration on AMD), HTTP authentication header or static mapping.

Client OS (id: browsOS)

The user's operating system.

Client region (id: cRegion)

Sites, areas, and regions define a logical grouping of clients and servers, or Backbone nodes in case of Synthetic Backbone reports, into a hierarchy. They are based on manual definitions and/or on clients' BGP Autonomous System names. Sites are the smallest groupings of clients and servers. Areas are composed of sites. Regions are composed of areas.

Client site (id: cLoc)

Sites, areas, and regions define a logical grouping of clients and servers, or Backbobne nodes in case of Synthetic Backbone reports, into a hierarchy. They are based on manual definitions, clients' BGP Autonomous System names, CIDR blocks or subnets. Sites are the smallest groupings of clients and servers. Areas are composed of sites. Regions are composed of areas.

Client site AS number (id: ASNum)

Client site's Autonomous System Number (ASN).

Client site description (id: cLocDescr)

The optional description of the client site, or a Backbobne node in case of Synthetic Backbone reports.

Client site ID (id: cLocDnsName)

In cases when sites are ASes, Client Site ID contains the AS number, which is also given in Client ASN, or Backbone node ASN in case of Synthetic Backbone reports. For manual sites, Client Site ID is identical to Client site, and contains the site name as defined in your site configuration. Sites based on CIDR blocks or subnets are identified by IP addresses.

Client site IP address (id: LocIP)

The client site IP address.

Client site type (id: cLocType)

One of site types: AS, Active, CIDR Block, Default, External, Manual, Network or Predefined. External is a site defined by a user in external configuration files. Manual site is defined by a user by means of configuration interface on the report server. Predefined sites are based on a mapping contained in a special configuration file.

Client site type ID (id: cLocTypeId)

Client site type ID

Client site UDL (id: clientLocUdl)

A dimension designed to filter only the User Defined Links. By default it is set to true (Yes) for WAN Optimization Sites report.

Client site WAN Optimized Link (id: clientLocWanOpt)

Indicates whether a site to which the client belongs is selected as both a UDL and a WAN optimized link.

Client type (id: browsN)

The user's browser type.

Client version (id: browsVer)

The version of the Internet browser used to execute the operation.

Client VPN (id: vpn)

The name of the VPN in which the user registered.

Client WINS name (id: cWINSName)

The client's computer name resolved by a WINS server.

Conference call id (id: voipConfCallId)

Identifier of the VoIP conference call.

Data source (id: dataProd)

The name of the data source in case you have configured a number of associated report servers to be used as data sources on the DMI screen.

Day of the week (id: dayOfWeek)

The textual representation of the day of the week.

Form name (id: pFormName)

Form name

Form title (id: pForm)

Form title

Grouping attributes 1 (id: serviceParam1)

One of the grouping attributes retrieved from a HTTP request or response, specific for a particular client. Requires configuration on AMD.

Grouping attributes 2 (id: serviceParam2)

One of the grouping attributes retrieved from a HTTP request or response, specific for a particular client. Requires configuration on AMD.

Grouping attributes 3 (id: serviceParam3)

One of the grouping attributes retrieved from a HTTP request or response, specific for a particular client. Requires configuration on AMD.

Hour of the day (id: hrD)

The numerical representation of the hour of the day, that is, numbers from 0 to 23.

Is duplicated? (id: duplicatedData)

Determines whether entity is duplicated.

Is front-end tier? (id: isFrontEndTier)

Indicates whether a given tier is a front-end tier for a selected application.

Is operation name cut? (id: isOperationCut)

Provides information if a presented operation name was cut by the AMD. Possible values: Yes, No.

Link alias (id: msrPoint4Cust)

A custom name created by a user for a selected link.

Link group (id: msrPointGr)

An element of the links hierarchy tree. May contain separate links or other link groups.

Link group level (id: msrPointGrLvl)

The hierarchy level on which a link group resides. The dimension differentiates only between 2 states: a link/group can either be on Level 1, or on any level different than Level 1.

Link monitor (id: msrPointWatch)

Link information source (Network Monitoring Probe, Flow Collector, AMD).

Link name (id: msrPoint)

A link name, as reported by the information source (Network Monitoring Probe, Flow Collector, AMD).

Link traffic direction (id: msrPointDir)

For traffic monitored with Netflow or NV WAN probes, this dimension says whether a client is on the far or near end from a point of view of a given interface.

  • If, for a specific interface, client bytes are incoming bytes, the direction bit is cleared (dimension value equals 0) and the client is on the far end from a point of view of this interface.

  • If client bytes are outgoing bytes, the direction bit is set (dimension value equals 1) and the client is on the near end from a point of view of this interface.

Link type (id: msrPointType)

The type of a monitored link, for example Ethernet or Frame Relay.

Location ID (id: locID)

Location ID

Miscellaneous parameter 1 (id: pUrlParam1)

One of the miscellaneous parameters retrieved from a base HTTP request or response. Requires configuration on AMD.

Miscellaneous parameter 2 (id: pUrlParam2)

One of the miscellaneous parameters retrieved from a base HTTP request or response. Requires configuration on AMD.

Miscellaneous parameter 3 (id: pUrlParam3)

One of the miscellaneous parameters retrieved from a base HTTP request or response. Requires configuration on AMD.

Miscellaneous parameter 4 (id: pUrlParam4)

One of the miscellaneous parameters retrieved from a base HTTP request or response. Requires configuration on AMD.

Miscellaneous parameter 5 (id: pUrlParam6)

One of the miscellaneous parameters retrieved from a base HTTP request or response. Requires configuration on AMD.

Miscellaneous parameter 6 (id: pUrlParam7)

One of the miscellaneous parameters retrieved from a base HTTP request or response. Requires configuration on AMD.

Module (id: pUrlURLHierarchyLvl2)

Module is the third level in the reporting hierarchy. For example, in database monitoring this is the database name, and in SOAP monitoring this is the SOAP service. This entity can be broken to smaller bits such as tasks.

Module (incl. whole) (id: pUrlNameSum)

Alias for the operation URL set on AMD's side or operation URL itself if alias is undefined. This dimension can assume values of a particular URL - if this URL is monitored - or it has the value "All" for all operations.

Network tier site selector (id: bgNetTier)

Displays only those client sites that are assigned to the selected network tier.

Operation (id: pUrl)

For HTTP, this is the URL of the base page to which the hit belongs. For other analyzers this can be a query, operation type or an operation status. Operation is ascertained by the AMD, based on referrer, timing relations between hits and per-transaction monitoring configured on the AMD. This dimension can assume values of a particular operation - if this operation is monitored. Note: The visibility of this dimension on reports depends on whether another dimension, related to servers - e.g. server IP or server DNS - has been used when formulating the query.

The All other operations record serves a catch-all net for al the traffic that has been seen to-from a server, but was not classified as belonging to a specific monitored-by-name operation. It accounts for statistics of:

  • operations which were not reported in per specific operation records (for example those that fall out of topN reported operations for a specific analyzer) - in such case the number of operations and slow operations, as well as operation time and other transactional statistics will be reported as an aggregate/average;

  • traffic which was not classified to any operations (for example, idle TCP session closure, TCP handshake without any operation, etc) - in such case only volumetric statistics (bytes, packets) will be reported for this specific traffic.

Operation (incl. whole) (id: pUrlSum)

For HTTP, this is the URL of the base page to which the hit belongs. For other analyzers this can be a query, operation type or an operation status. Operation is ascertained by the AMD, based on referrer, timing relations between hits and per-transaction monitoring configured on the AMD. This dimension can assume values of a particular operation - if this operation is monitored. Note: The visibility of this dimension on reports depends on whether another dimension, related to servers - e.g. server IP or server DNS - has been used when formulating the query. Compare "Operation (incl. whole)".

Operation (not aliased) (id: pUrlNoAlias)

The original operation name as seen in the traffic.

Operation name (id: pTransName)

The name of the operation.

Operation status (id: pSapTrans)

SAP GUI transaction code (T-Code) combined with SAP GUI window name and SAP GUI status.

Operation type (id: pTrans)

The name of the operation type.

Page name (id: pUrlPageName)

Alias for the page URL set on AMD's side or page URL itself if alias is undefined.

Parent reporting group (obsolete) (id: bgParent)

An application that acts as a "container" for a specific transaction.

Parent reporting group type (obsolete) (id: rptParentGrType)

Currently, a parent reporting group can only be an application, which acts as a parent reporting group for transactions.

Physical link name (id: physMsrPoint)

The first of 2 segments in a link name.

Process ID (id: processId)

The identifier of a process running on a Citrix server on which Cerner applications are running.

Protocol (id: protocol)

The IP protocol name.

Query name (id: pQueryName)

Alias for the query set on AMD's side or query itself if alias is undefined.

Query text (id: pQuery)

Shortened SQL query representation, preprocessed by AMD.

Query text (incl. whole) (id: pQuerySum)

This dimension can assume values of a particular query - if this query is monitored - or it has the value "All" for all queries.

Reporting group (id: repGroup)

Reporting group is a universal container that can accommodate software services, servers, URLs or any combination of these. Reporting groups can contain software services of every type. Advanced Diagnostics Server can import reporting group configuration from Central Analysis Server.

Reporting group (obsolete) (id: bgname)

Reporting group is a universal container that can accommodate software services, servers, URLs or any combination of these. Reporting groups can contain software services of every type. Advanced Diagnostics Server can import reporting group configuration from Central Analysis Server.

Reporting group type (obsolete) (id: rptGrType)

A reporting group, application, transaction, SOAP service or SOAP method.

Request method (id: reqMet)

The HTTP request type: GET or POST.

SAP operation order (id: stepSeqNo)

The sequence number of a step is used to set the relation between operations and tasks. It is unique only within the scope of a given task.

Script name (id: scriptName)

The name of the Universal Decode script.

Server aggregated name (id: sAggrName)

Server aggregated name

Server area (id: sLocArea)

Sites, areas, and regions define a logical grouping of clients and servers into a hierarchy. They are based on manual definitions and optionally on clients' BGP Autonomous System names, CIDR blocks or subnets. Sites are the smallest groupings of clients and servers. Areas are composed of sites. Regions are composed of areas.

Server city (id: sGeoCity)

Geographical data about the server site.

Server country (id: sGeoCountry)

Geographical data about the server site.

Server geographical region (id: sGeoRegion)

Geographical data about the server site.

Server ID (id: svrID)

Server ID

Server identifier (id: sIdentifier)

Server identifier

Server identifier type (id: sIdType)

Server identifier

Server identifier with DNS name (id: sIdWithDns)

Server identifier

Server IP address (id: sIP)

The IP address of the server.

Server name (id: sDNSName)

The name of the server resolved by a DNS server.

Server port (id: sPort)

The TCP port number on a server that hosts a software service.

Server region (id: sRegion)

Sites, areas, and regions define a logical grouping of clients and servers into a hierarchy. They are based on manual definitions and/or on clients' BGP Autonomous System names. Sites are the smallest groupings of clients and servers. Areas are composed of sites. Regions are composed of areas.

Server site (id: sLoc)

Sites, areas, and regions define a logical grouping of clients and servers into a hierarchy. They are based on manual definitions and/or on clients' Autonomous System names. Sites are the smallest logical structures that comprise of clients and servers. Areas are composed of sites, and regions are composed of areas.

Server site description (id: sLocDescr)

Optional description of the server site.

Server site ID (id: sLocDnsName)

In cases when sites are ASes, Server site ID contains the AS number, which is also given in Server ASN. For manual sites, Server site ID is identical to Server site, and contains the site name as defined in your site configuration. Sites based on CIDR blocks or subnets are identified by IP addresses.

Server site WAN Optimized Link (id: sLocWanOpt)

Indicates whether a site to which the server belongs is selected as both a UDL and a WAN optimized link.

Service (id: pUrlURLHierarchyLvl3)

Service is the highest level of multi-level reporting hierarchy. For example, in SAP GUI monitoring this is the business process. This entity can be broken to smaller bits such as modules.

Software service (id: appl)

The software service name, where by a software service we understand a service implemented by a specific piece of software, offered on a TCP or UDP port of one or more servers and identified by a particular TCP port number.

Software service class (id: applClass)

Software service class

Software service ID (id: applID)

Software service ID

Software service type (id: applType)

Software service type

Storage source (id: storageSource)

Storage source

Task (id: pUrlURLHierarchyLvl1)

Task is the second level in the reporting hierarchy. For example, in HTTP monitoring this is the page name; in database monitoring this is the operation name (may contain regular expression if configured on the AMD) or operation type prefix, and in SOAP monitoring this is the SOAP method. This entity can be broken to smaller bits such as operations or operation types.

Task (obsolete) (id: pUrlName)

Task is the second level in the reporting hierarchy. For example, in HTTP monitoring this is the page name; in database monitoring this is the operation name (may contain regular expression if configured on the AMD) or operation type prefix, and in SOAP monitoring this is the SOAP method. This entity can be broken to smaller bits such as operations or operation types.

Tier (id: bgnameTier)

A specific point of the application where we measure data. It can be a specific traffic type or a server.

Tier (obsolete) (id: rptGrBoundByMap)

A specific point of the application where we measure data. It can be a specific traffic type or a server.

Tier sequence number (id: bgnameTierSeqNum)

The sequence number of a tier is determined by the order in which you define your tiers, and these numbers in turn determine the order in which data is displayed on the report.

Tier type (id: bgnameTierType)

The type of a tier can be one of the following: client, network, or data center.

Time (id: begT)

The time stamp of the data presented on the report.

TOS-binary (id: applBinTOS)

A traffic identifier contained in an 8-bit field in the IP packet header. The contents of this field can be detected by the AMD and displayed in reports. The use of this field is software service specific; it is used by software services to denote special types of traffic.

TOS-decimal (id: tos)

A traffic identifier contained in an 8-bit field in the IP packet header. The contents of this field can be detected by AMD and displayed in reports. The use of this field is software service specific: it is used by software services to denote special types of traffic.

Traffic type (id: realsynth)

The type of client traffic: real or synthetic, that is, generated by a synthetic agent.

Transaction (id: bgTrans)

A universal container that can accommodate operations. This metric refers only to transactions without errors.

Transaction step (id: bgBussStep)

The step as configured in a transaction definition. Step configuration is built on DCRUM data using operations, tasks, modules or services. Steps are contained within transactions and carry the entire transaction configuration.

Transaction step sequence number (id: bgBussStepSeqNum)

The sequence number of a step is used for presentation purposes. It marks the order of a particular step in a transaction configuration. You can order steps within each transaction if such an ordering makes sense for the overall monitored application paradigm. The transaction step sequence does not affect data aggregation.

URL host (id: pUrlHost)

The domain name, including the port number (if it is reported by the AMD).

URL ID (id: urlID)

URL ID

URL path (id: pUrlPath)

The request path that points to a Web resource, including the first forward slash.

URL protocol (id: pUrlProtocol)

The protocol that is used to locate the resource (HTTP or HTTPS).

User group (id: userGr)

The name of the users group.

User ID (id: userID)

User ID

User name (id: userN)

Client's name determined from HTTP cookie (requires configuration on AMD), HTTP authentication header or static mapping.

VC link name (id: vcMsrPoint)

The second of 2 segments in a link name.

Software service, operation, and site data metrics

% of bad delay calls

The percentage of VoIP calls with delay above the acceptable level.

% of bad jitter calls

The percentage of VoIP calls with jitter exceeding the acceptable level.

% of bad lost packets calls

The percentage of VoIP calls with loss rate above the acceptable level.

% of bad MOS calls

The percentage of VoIP calls with the Mean Opinion Score (MOS) rating below acceptable threshold.

% of bad R-factor calls

The percentage of VoIP calls with R-factor value below the acceptable value.

Aborted page Application Delivery Channel Delay

Application Delivery Channel Delay in tenths of milliseconds for an aborted page.

Aborted page http server time

A time difference between the response and request for an aborted page.

Aborted page image server time

The average combined image server time (HTTP) for an aborted page.

Aborted page redirect time

The average redirect time per operation (this includes operations with no redirects).

Aborted page request size

The average aborted client request size (GET or POST).

Aborted page request time

The average time from the first client SYN packet to the last request packet for an aborted operation.

Aborted page server delay

The time spent on the server during one operation.

Aborted page size in bytes

The average aborted operation size in bytes.

Aborted page SSL setup time

The average SSL setup time per operation.

Aborted page TCP connect time

The average TCP connect time for an aborted operation. Counted as an average of TCP connection times. A single TCP connection time is counted as the time difference between the first client SYN and first client ACK.

Aborted page transfer time

The average time it took the server to send a response to the client, averaged over all the aborted operations in the monitoring interval.

Aborts

The number of operations aborted by the client. It applies to all TCP-based protocols. For example, for HTTP/HTTPS, it is the number of operations manually stopped by the user by either clicking on the Stop or Refresh buttons or selecting another URL. Note that, in the case of HTTP, this number includes Short aborts and Long aborts.

ACK RTT

The time it takes for an ACK packet to travel from a user/client to the monitored server and back again.

Activity time

The amount of time the server or client has been active, that is, transmitted any traffic. The time resolution is equal to the length of the monitoring interval.

Affected clients (application)

The number of clients that experienced application performance problems. For transactional protocols, a problem is noted if at least one operation is completed in time longer than the performance threshold. For transactionless TCP-based protocols, a problem is noted if user wait per kB of data is longer than the threshold value.

Affected clients (availability)

The number of unique clients that were affected by the availability related problems.

Affected clients (network)

The number of unique clients that experienced network performance problems.

Affected users (availability)

The number of unique users that were affected by the availability problems.

Affected users (availability) breakdown

A breakdown of users into how many were affected by availability problems and how many were not.

Affected users (network)

The number of unique users that experienced network performance problems.

Affected users (network) breakdown

A breakdown of users into how many were affected by network performance problems and how many were not.

Affected users (performance)

The number of users that experienced application performance problems. For transactional protocols, a problem is noted if at least one operation is completed in time longer than the performance threshold. For transactionless TCP-based protocols, a problem is noted if user wait per kB of data is longer than the threshold value.

Affected users (performance) breakdown

A breakdown of users into how many were affected by application performance problems and how many were not.

Aggregate data center time

This is a sum of all products: server time multiplied by the number of transactions.

Application Delivery Channel Delay

In WAN optimized scenario, Application Delivery Channel Delay (ADCD) is a quality metric represented in milliseconds. The ADCD is determined by initial observation of the traffic between a client and a server. ADCD is a derivative of RTT measured on a WAN link expressed in time and as such it can be understood as latency, where the larger ADCD would indicate a higher network latency. ADCD also includes time spent in the data center WOC for traffic buffering and processing. A change of ADCD from its initial value reflects a change of quality in WAN optimization service. For example, sudden increase of ADCD would suggest that the quality of the service has worsened and conversely, a sudden decrease of ADCD value could suggest an improvement in WAN optimization.

Application health index

The percentage of fast operations calculated as "Fast Operations / (Failures + Operations) * 100%".

Application Monitoring Flags

One of 0,1 or 2, meaning: 0 - no Application Monitoring servers, 1 - one Application Monitoring server, 2 - several Application Monitoring servers.

Application Monitoring Hits

The number of Application Monitoring hits.

Application Monitoring Operations

The number of Application Monitoring operations.

Application Monitoring Server Errors

The number of Application Monitoring server errors.

Application performance

For transactional protocols, this is the percentage of software service operations completed in a time shorter than the performance threshold. For SMTP and transactionless TCP-based protocols, this is the percentage of monitoring intervals in which user wait time per kB of data was shorter than the threshold value.

Application performance affected bytes

Application performance affected bytes

Application performance relevant bytes

Application performance relevant bytes

Attempts

The number of monitoring intervals during which attempts were made to connect to a server. Note that this is counted separately for each server, client and software service. Thus, if in a given monitoring interval there are attempts to connect to three different servers, the Attempts metric will be incremented by three for that one monitoring interval. The actual value shown on the report is the sum total of all the attempts, for all the monitoring intervals, in the period covered by the report.

Attempts (transport)

The total number of transactions, including transactions with errors.

Auto-discovery flags

If a software service contains any autodiscovered traffic, the metric displays the green tick sign.

Availability (application)

Availability limited to the application context, calculated using the following formula:

Availability (application) = 100% * (All Attempts – Failures (Application) / All Attempts

where

All attempts = all failures + all successful operations + all standalone hits not classified as a failure + all aborts not classified as a failure.

Availability (TCP)

Availability limited to the network context, calculated using the following formula:

Availability (application) = 100% * (All Attempts – Failures (TCP) / All Attempts

where

All attempts = all failures + all successful operations + all standalone hits not classified as a failure + all aborts not classified as a failure.

Availability (total)

The percentage of successful attempts, calculated using the following formula:

Availability (total) = 100% * (All Attempts – All failures) / All Attempts

where

All attempts = all failures + all successful operations + all standalone hits not classified as a failure + all aborts not classified as a failure

All failures = all failures (transport) + all failures (TCP) + all failures (application).

Availability (transport)

Availability limited to the transport context, calculated using the following formula:

Availability (application) = 100% * (All Attempts – Failures (Transport) / All Attempts

where

All attempts = all failures + all successful operations + all standalone hits not classified as a failure + all aborts not classified as a failure.

Bad delay calls

The number of VoIP calls with delay above the acceptable level.

Bad jitter calls

The number of VoIP calls with jitter exceeding the acceptable level.

Bad lost packets calls

The number of VoIP calls with loss rate above the acceptable level.

Bad MOS calls

The number of VoIP calls with the Mean Opinion Score (MOS) rating below acceptable threshold.

Bad R-factor calls

The number of VoIP calls with R-factor value below the acceptable value.

Call attempts

The number of call attempts including successful and failed ones.

Call duration

The time the VoIP call took.

Calls

The total number of VoIP calls. Note that for a selected software service the number of calls as seen from the sites' perspective may differ from the number seen from the endpoints' perspective. This is because in one site we may have two users taking part in the same call.

Calls finished with termination error

The number of calls that finished with the termination error.

Calls not started due to remote peer

The number of calls that could not start due to a remote peer.

Calls with error during begin phase

The number of calls affected by errors occurring during the begin phase.

Change from Average - last 10 days

Change from Average - last 10 days

Client ACK RTT

Client ACK RTT is the time it takes for an ACK packet with no payload to travel from the user to the AMD and back again.

Client ACK RTT measurements

This metric keeps track of how many Client ACK RTT measurements were made. ACK measurement is performed during ACK packet transmission either from server or client side of the transaction.

Client bandwidth usage

The number of client bits per second.

Client bytes

The number of bytes sent by the clients. Note that this includes headers.

Client IP addresses (type)

This metric indicates if the reported observations are associated with one or more IP addresses. It assumes the value "multiple" or an IP address. In DMI queries, such metrics should be used in conjunction with a client name or IP address, else this metric will most likely always have the value "multiple".

Client loss rate

The percentage of total packets sent by a client that were lost (due to network congestion, low router queue capacity or other reasons) and needed to be retransmitted.

Client loss rate (AMD to server)

The percentage of total packets sent by a client that were lost - between the server and the AMD - and needed to be retransmitted.

Client loss rate (client to AMD)

The percentage of total packets sent by a client that were lost - between the client and the AMD - and needed to be retransmitted.

Client not responding errors

The number of errors of category Client not responding.

Errors of this category occur when the server closes the TCP session with a RESET packet after the client has been idle for too long. Such a situation happens when the server TCP/IP stack detects that network connection to the client exists, but the client remains idle and does not respond. In such a case, the server closes the TCP session with a RESET packet. This may occur when the client has been silently disconnected from the network, for example, due to link failure, or the client has crashed. Note that this error will not occur if the client session has ended gracefully, that is, by closing the client application.

Client operations

The number of operations (for HTTP/SSL this is equivalent to the number of pages, for DB/2 it is equivalent to the number of queries) from the client side. For traffic analyzed with the analyzers General-volume and ICA (Citrix), this is the number of client data transfers for which network realized bandwidth was measured.

Client operation size

The size of a client operation. Note: an operation can be split over several packets. For traffic parsed with HTTP and SSL decrypted analyzers, Client operation size is the size in bytes of the operation request (HTTP GET or POST).

Client packets

The number of packets sent by the clients.

Client packets/sec

The number of packets per second, sent by the clients.

Client packet size

The average size of the client-originating packets (in bytes), including header.

Client packets lost (AMD to server)

The number of packets sent by a client that were lost - between the AMD and the server - and needed to be retransmitted.

Client packets lost (client to AMD)

The number of packets sent by a client that were lost - between the client and the AMD - and needed to be retransmitted.

Client realized bandwidth

Client realized bandwidth refers to the actual transfer rate of client data when the transfer attempt occurred, and takes into account factors such as loss rate (retransmissions). Thus, it is the size of an actual transfer divided by the transfer time.

Client retransmission timeouts

Number of times retransmission timeout occurred on client connection. Calculated only for AppFlow records collected by AMD from NetScaler.

Client RTT

Client RTT is the time it takes for a SYN packet (sent by a server) to travel from the AMD to the client and back again, as shown in the following picture.

graphical illustration

A client RTT measurement begins when the SYN ACK packet from the server to the client passes by the AMD (T5). The packet reaches the client machine (T6) and is processed, while an acknowledgment is sent back to the server (T7). Client processing time impact (T7-T6) is again very low. Client RTT measurement ends when the ACK packet reaches the AMD (T8). Therefore, the Client Round Trip Time is calculated as T8-T5. Depending on the actual setup, Client RTT measurements may vary dramatically. In corporate environments, it may be a few milliseconds for LAN-connected clients or a couple dozens milliseconds for WAN-connected clients. In this case, where the client is coming from the Internet, the end-to-end Client RTT measurement is a compound of transit time through the Internet backbone as well as through the "last mile" access network. The impact of the last mile can be easily calculated, based on the connection speed and the packet size (56B in case of TCP SYN packet). For a 28 kbps dial-up connection, this amounts to 16 milliseconds one way, or 32 milliseconds for a complete round-trip measurement. For a 1.6 Mbps DSL line, this makes 56 microseconds towards complete client RTT measurement.

Client TCP data packets

The total number of TCP packets sent by the clients, excluding the traffic control packets.

Client TCP data packets lost

The number of lost TCP data packets sent by the clients, excluding the traffic control packets. The number of lost TCP packets always regards the context of the counter, for example, an application, a server or any other entity.

Closed TCP connections

The total number of successful or failed TCP connections.

Connection establishment timeout errors

The number of TCP errors of category Connection establishment timeout errors. This category of errors applies when there was no response from the server to the SYN packets transmitted by the client.

Connection refused errors

The number of TCP errors of category Connection refused errors, also referred to as Session establishment errors. This category of errors applies when a server rejects a request from a client to open a TCP session. Such a situation usually happens when the server runs out of resources, either due to operating system kernel configuration or lack of memory.

Custom metric (1)(avg)

The average value of user-defined metrics in category 1 observed in the HTTP or XML traffic.

Custom metric (1)(cnt)

The number of occurrences of user-defined metrics in category 1 observed in the HTTP or XML traffic.

Custom metric (1)(sum)

The sum of all values of user-defined metrics in category 1 observed in the HTTP or XML traffic.

Custom metric (2)(avg)

The average value of user-defined metrics in category 2 observed in the HTTP or XML traffic.

Custom metric (2)(cnt)

The number of occurrences of user-defined metrics in category 2 observed in the HTTP or XML traffic.

Custom metric (2)(sum)

The sum of all values of user-defined metrics in category 2 observed in the HTTP or XML traffic.

Custom metric (3)(avg)

The average value of user-defined metrics in category 3 observed in the HTTP or XML traffic.

Custom metric (3)(cnt)

The number of occurrences of user-defined metrics in category 3 observed in the HTTP or XML traffic.

Custom metric (3)(sum)

The sum of all values of user-defined metrics in category 3 observed in the HTTP or XML traffic.

Custom metric (4)(avg)

The average value of user-defined metrics in category 4 observed in the HTTP or XML traffic.

Custom metric (4)(cnt)

The number of occurrences of user-defined metrics in category 4 observed in the HTTP or XML traffic.

Custom metric (4)(sum)

The sum of all values of user-defined metrics in category 4 observed in the HTTP or XML traffic.

Custom metric (5)(avg)

The average value of user-defined metrics in category 5 observed in the HTTP or XML traffic.

Custom metric (5)(cnt)

The number of occurrences of user-defined metrics in category 5 observed in the HTTP or XML traffic.

Custom metric (5)(sum)

The sum of all values of user-defined metrics in category 5 observed in the HTTP or XML traffic.

Database errors

The number of database errors in the database analyzer:

  • For TDS, which includes Sybase and MS SQL Server, any value from the following table is considered an error.

  • For MySQL, if an ERR_Packet is returned, the error count is incremented.

An error with a severity level of 19 or higher stops the execution of the current SQL batch and the error message is written to the error log.

Errors that can be corrected by the user:

11: The given object or entity does not exist.

12: SQL statements that do not use locking because of special options. In some cases, read operations performed by these SQL statements could result in inconsistent data, because locks do not guarantee consistency.

13: Transaction deadlock errors.

14: Security-related errors such as permission denied.

15: Syntax errors in the SQL statement.

16: General errors that can be corrected by the user.

Software errors that cannot be corrected by the user and that require system administrator action:

17: The SQL statement caused the database server to run out of resources (such as memory, locks, or disk space for the database) or to exceed some limit set by the system administrator.

18: There is a problem in the database engine software, but the SQL statement completes execution, and the connection to the instance of the database engine is maintained. System administrator action is required.

19: A non-configurable database engine limit has been exceeded and the current SQL batch has been terminated.

System problems:

20-25: Fatal errors, meaning that the database engine task that was executing a SQL batch is no longer running. The task records information about what occurred and then terminates. In most cases, the application connection to the instance of the database engine also terminates. If this happens, depending on the problem, the application might not be able to reconnect.

Database warnings

The number of database warnings in the database analyzer:

  • For TDS, which includes Sybase and MS SQL Server, this count will always be zero. TDS does not track anything as a warning.

  • For MySQL, if an OK_Packet is returned, the warning count value in that packet is checked and the total warning field is updated with the returned number.

Data samples

The number of lines in the traffic performance data packages received from the AMDs. When clients are aggregated into so-called aggregation blocks, this is the number of software service-server-site triplets. This metric is not calculated in PVU mode.

Delay

Data transfer delay on a DataCenter device, such as load balancer or firewall.

Discarded aborts

The number of aborted hits without valid server response.

DNS errors

The number of DNS errors.

DNS format errors

The number of DNS format errors (DNS error code 1).

DNS name errors

The number of DNS name errors (DNS error code 3).

DNS not implemented errors

The number of DNS not-implemented errors (DNS error code 4).

DNS other errors

The number of DNS errors with error codes from 6 to 15, that is errors that do not fall into any of the following categories: DNS format errors (error code 1), DNS server failure errors (error code 2), DNS name errors (error code 3), DNS not implemented errors (error code 4), DNS refused errors (error code 5), DNS timeouts.

DNS refused errors

The number of DNS refused errors (DNS error code 5).

DNS server failure errors

The number of DNS server failure errors (DNS error code 2).

DNS timeouts

The number of DNS timeout errors.

E-mail size

The average e-mail message size.

E-mail transfer time

The average value of e-mail transfer time.

E-mail transfer time breakdown

The breakdown of the average value of e-mail transfer time into server time and network time.

E-mail transfer time percentage breakdown

The breakdown of the average value of e-mail transfer time into percentages of server time and network time.

Endpoints A

If voice data is provided by Network Monitoring Probe, this is the total number of callers detected during a given monitoring interval.

Endpoints B

If voice data is provided by Network Monitoring Probe, this is the total number of recipients detected during a given monitoring interval.

End-to-end ACK RTT

The time it takes for an ACK packet to travel from a client to the monitored server and back again.

End-to-end RTT

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

Error indicator

The number of error indicators.

Errors

The total number of errors.

Error sessions

The total number of Client not respondingand Server not responding errors, that is sessions when the server closes the TCP session with a RESET packet after the client has been idle for too long, or when the client closes the TCP session with a RESET packet after the server has failed to respond for too long.

Excluded operations

The number of operations for which the operation time was above a safety threshold. The term "operations" refers to operations in the context of the particular protocol, and can mean HTTP/HTTPS page loads, database queries, XML (transactional services) operations, Jolt transactions on a Tuxedo server, e-mails, DNS requests, Oracle Forms submissions, MQ operations, VoIP calls, MS Exchange operations, or SAP operations.

Failed TCP connection attempts

The number of failed TCP connection attempts.

Failures (application)

The number of operation attributes of all types set to be reported as an application failure.

Failures (TCP)

The total number of operations that failed due to Connection refused or Connection establishment timeout errors.

Failures (total)

The total number of failures, that is all Failures (transport) + all Failures (TCP) + all Failures (application)

Failures (transport)

The number of operations that failed due to the problems in the transport layer. These include protocol errors, SSL alerts classified as a failure, incomplete responses selected be classified as failures.

Fast form submissions

The number of Oracle Forms submissions not qualified as slow.

Fast form submissions per minute

The number of Oracle Forms submissions not qualified as slow, per minute.

Fast operations

The number of operations for which the operation time was below a predefined threshold value. The term "operations" refers to operations in the context of the particular protocol, and can mean HTTP/HTTPS page loads, database queries, XML (transactional services) operations, Jolt transactions on a Tuxedo server, e-mails, DNS requests, Oracle Forms submissions, MQ operations, VoIP calls, MS Exchange operations, or SAP operations.

Fast operations per minute

The rate of operations (number per minute) for which the operation time was below a predefined threshold value. The term "operations" refers to operations in the context of the particular protocol, and can mean HTTP/HTTPS page loads, database queries, XML (transactional services) operations, Jolt transactions on a Tuxedo server, e-mails, DNS requests, Oracle Forms submissions, MQ operations, VoIP calls, MS Exchange operations, or SAP operations.

Fast pages

The number of HTTP/HTTPS operations for which the load time was below a predefined threshold value.

Fast pages per minute

The rate (number per minute) of HTTP/HTTPS operations for which the load time was below a predefined threshold value.

Fast queries

The number of database queries for which the query time was below a predefined threshold value.

Fast queries per minute

The rate (number per minute) of database queries for which the query time was below a predefined threshold value.

Fast requests

The number of DNS requests with the request time below a predefined threshold value.

Fast requests per minute

The number of DNS requests with the request time below a predefined threshold value, per minute.

Fast responses

The number of fast DNS responses per minute (by default, loaded in less than 8 seconds).

Fast responses per minute

The number of fast DNS responses per minute (by default, loaded in less than 8 seconds), per minute.

Fatal error

The number of fatal errors.

Form breakdown

Form breakdown into numbers of slow and fast form submissions.

Form percentage breakdown

Form percentage breakdown into slow and fast form submissions.

Forms application error

The number of Oracle Forms application errors that occurred during a given operation. For a complete list of specific Forms application errors, refer to the RUM Console Help.

Forms client error

The number of Oracle Forms client errors that occurred during a given operation. For a complete list of specific Forms client errors, refer to the RUM Console Help.

Form size

The average form size expressed in bytes.

Forms server error

The number of Oracle Forms server errors that occurred during a given operation. For a complete list of specific Forms server errors, refer to the RUM Console Help.

Form submissions

The number of Oracle Forms submissions detected during the reported period.

Form submissions per minute

The number of Oracle Forms submissions per minute.

Form submission time

The average value of the form submission time.

Form submission time breakdown

The breakdown of the average value of the form submission time into server time and network time.

Form submission time percentage breakdown

The breakdown of the average value of the form submission time into percentages of server time and network time.

Hits

The number of subcomponents of error-free operations. Note that this metric is recorded at the time when the monitored operations are closed. In case of HTTP, it is when the whole page has been loaded. Compare "Hits (started)". For example, when the user issues an HTTP GET, a "Hit (started)" is reported immediately, whereas if a whole page is loaded and the operation is closed, it is reported as a "Hit".

Hits (started)

The number of subcomponents of operations. Unlike the "Hits" metric, "Hits (started)" is recorded immediately, not at the end of an operation. For example, when the user issues an HTTP GET, a "Hit (started)" is reported immediately, whereas if a whole page is loaded and the operation is closed, it is reported as a "Hit".

Hits (started) for the whole server

The number of subcomponents of operations, for the whole server. Note that this metric is recorded immediately and not at the end of an operation. Compare "Hits". For example, when a user issues an HTTP Get, this is reported immediately as a "Hit (started)". If this does not result in an HTTP error, it is recorded as a "Hit", when the operation is closed, which in case of HTTP is when the whole page has been loaded.

Hits (succeeded)

The number of hits, that did not generate client or server errors (replies in range 2xx and 3xx).

Hits per operation

The number of hits per operation.

HTTP availability

The percentage of successful HTTP hits, calculated based on the following formula:

100 * (Hits - HTTP errors) / Hits

All HTTP errors are taken into account.

HTTP client errors (4xx)

The sum of all HTTP client errors (4xx).

This includes 4 categories of errors (4xx), by default HTTP Unauthorized (401, 407) errors, HTTP Not Found (404) errors, custom client (4xx) errors and Other HTTP (4xx) errors. The contents of the first 3 categories can be configured by users.

However, there are two types of the 4XX errors that are of particular importance: errors 401 related to server-level authentication, and errors 404 indicating requests for non-existent content. These two error types are reported separately, by specific metrics.

  • 401 Unauthorized - Server reports this error when user's credentials supplied with request do not satisfy page access restrictions. The HTTP server layer, not the application layer, reports 401 errors. The AMD will report on "Unauthorized" errors only if server-level authentication has been configured. This is common practice for sites that are comfortable with very basic user access policies. Most commercial-grade applications do not rely on server-level authentication (e.g. most of online banking applications or online shopping), but rather authenticate users on the application layer. In such a case, even if authentication fails, the server will typically send 200 OK responses and authentication error information will be explained in page content. So this kind of error is not very common in commercial sites.

  • 404 Not Found - Server reports "Not Found" errors when it cannot fulfill client request for a resource. Usually it happens due to malformed URL, which directs to a non-existing page or image. Such a URL request may result from a user, who misspelled the URL, trying to access a URL that the user stored in his "Favorites" folder a long time ago, or some other mistake. Malformed URLs may also exist in invalid or incorrectly designed Web pages so the error will be reported by browsers trying to load such a page. Significant and constant number of these errors usually indicates that some pages on the server have design-related or link validation issues. In some cases, 404 errors result from the server overload. It is good practice to check whether the percentage of errors is load-related.

HTTP client errors (4xx) percentage

The percentage of all HTTP client errors (4xx).

HTTP client errors - category 3 (default name)

The number of HTTP custom client errors (4xx). By default, there is no specific error type assigned here.

HTTP errors

The number of observed HTTP client errors (4xx) and server errors (5xx).

HTTP not found errors 404 (default name)

The number. These include the observed custom HTTP 404 Not found errors.

HTTP other client errors (4xx)

The number of HTTP other client errors (4xx).

There are four categories of HTTP client errors (4xx), of which three can be configured by users. By default, the first category includes HTTP Unauthorized (401, 407) errors, the second category - HTTP Not Found (404) errors. The third category contains no default error types assigned, and can be configured by a user. Finally, a group of HTTP Other (4xx) errors contains all errors that do not fall into any other client errors category.

The number is calculated based on the formula: [HTTP errors 4xx] - [HTTP Not Found errors 404] - [HTTP Not Authorized (401+ 407)] - [HTTP errors configured by user].

HTTP other client errors (4xx) percentage

The percentage of HTTP other client errors (4xx). See the definition of the HTTP other client errors (4xx) metric for details.

HTTP other server errors (5xx)

The number of HTTP server errors (5xx) that do not fall into categories 1 or 2 of custom HTTP server errors (5xx).

HTTP other server errors (5xx) percentage

The percentage of HTTP server errors (5xx) that do not fall into categories 1 or 2 of custom HTTP server errors (5xx).

HTTP redirect time

The average amount of time that was spent between the time when a user went to a particular URL and the time this user was redirected to another URL and issued a request to that new URL. The HTTP redirect time refers to the transactions for which redirection actually took place.

HTTP response time

This is the amount of time it takes for a server to provide its initial response to a user's operation request. Often servers will respond with some information quickly, before all the information is ready for delivery. "HTTP server time" is equal to or smaller than "Server time".

HTTP server errors (5xx)

The number of observed HTTP server errors (5xx).

The response status codes 5xx indicate cases, in which the Web server is aware that there was a server error or it is incapable of performing the request. Such error presence usually means that the Web server does not function as intended. The following 5xx errors are defined by the HTTP protocol standards:

  • 500 Internal Server Error - The server encountered an unexpected condition, which prevented it from fulfilling the request.

  • 501 Not Implemented - The server does not support the functionality required to fulfill the request.

  • 502 Bad Gateway - The server received an invalid response from a back-end application server.

  • 503 Service Unavailable - The server is currently unable to handle the request due to a temporary overloading or maintenance of the server.

  • 504 Gateway Timeout - The server did not receive response from a back-end application server.

  • 505 HTTP Version Not Supported - The server does not support the HTTP protocol version that was used in the request message.

HTTP server errors (5xx) percentage

The percentage of all observed HTTP server errors (5xx).

HTTP server errors – category 1 (default name)

The number of custom HTTP server errors (5xx), category 1. By default, there are no specific error types assigned to this category.

HTTP server errors – category 2 (default name)

The number of custom HTTP server errors (5xx), category 2. By default, there are no specific error types assigned to this category.

HTTP server image time

This is the total amount of time it takes for images (non-HTML content) to be prepared for delivery.

HTTP unauthorized errors 401, 407 (default name)

The number of observed custom HTTP authentication related errors.

These include "HTTP 401 Unauthorized" and "HTTP 407 Proxy authentication required" errors.

HTTP servers generate errors "401 Unauthorized" in cases, when anonymous clients are not authorized to view the requested content and must provide authentication information in the WWW-Authenticate request header. The 401 errors are similar to "403 Forbidden" errors, however used when authentication is possible but it has failed or not yet been provided. The 407 error is basically similar to 401, but it indicates that the client should first authenticate with a proxy server.

The AMD will report these errors only if the server-level authentication has been configured. Simple and basic user access policies are common in Web sites that do not store user-sensitive and/or business critical information.

Most commercial-grade applications, based on HTTP, such as home banking applications or online shopping sites, rely on the application-level authentication rather than the server-level authentication. Such applications are designed in the way that even if the user authentication fails, the HTTP server usually sends the 200 OK response code and the authentication error message in the page content. Therefore, the 401 Unauthorized and 407 Proxy authentication required error codes are quite rare in commercial environments.

Idle sessions

The number of idle TCP sessions, that have not been active for a period of time longer than a predefined time-out time, 5 minutes by default.

Idle time

The part of the operation time spent between receiving a part of the response and requesting a subsequent part. It enables you to isolate the time taken by client from the time when the data was still being transmitted on the network

Incomplete Responses

The number of incomplete responses, that is partial and server aborted responses, as well as situations when a server did not respond to the request at all or responded in an urecognizable way.

Is configured?

Indicates whether it is a user-defined software service configured on an AMD. If not, the column displays the red X sign. If a row presents the data for an aggregated server, the column displays the question mark.

LAN-WAN byte ratio

The amount of compression performed and expressed as a percentage.

  • 100% for pass-through.

  • Greater than 100% if more bytes on the WAN side, including both pass-through and optimized traffic.

  • Less than 100% if fewer bytes on the WAN side, including both pass-through and optimized traffic.

LAN-WAN packet ratio

The amount of compression performed and expressed as a percentage, where a lower packet count on the WAN side means lower compression.

  • 100% for pass-through.

  • Greater than 100% if more packets on the WAN side, including both pass-through and optimized traffic.

  • Less than 100% if fewer packets on the WAN side, including both pass-through and optimized traffic.

This metric is hidden by default.

LDAP client error

LDAP client error

  • Time Limit Exceeded

LDAP critical error

LDAP critical errors

  • Busy

  • Unwilling To Perform

  • Operation Error

  • Size Limit Exceeded

  • Constraint Violation

  • Protocol Error

  • Invalid Attribute Syntax

  • Naming Violation

  • Invalid Credentials

LDAP errors

The number of LDAP Erros. The LDAP Errors are reported in the following categories:

  • LDAP critical errors

  • LDAP server errors

  • LDAP security errors

  • LDAP syntax errors

  • LDAP client error

  • LDAP client error

LDAP security error

LDAP security errors

  • Authentication Method Not Supported

  • Stronger Auth Required

  • Admin Limit Exceeded

  • Confidentiality Required

  • Inappropriate Authentication

  • Insufficient Access Rights

  • Object Class Mods Prohibited

LDAP server error

LDAP server errors

  • Unavailable

  • Loop Detect

  • Not Allowed On NonLeaf

  • Not Allowed On RDN

  • Affects Multiple DSAs

  • Other

  • Referral

  • Unavailable Critical Extension

  • SAS Binding Progress

  • No Such Object

  • Alias Problem

  • Invalid DN Syntax

  • Alias Dereferencing Problem

LDAP syntax error

LDAP syntax errors

  • Compare False

  • Compare True

  • No Such Attribute

  • Undefined Attribute Type

  • Inappropriate Matching

  • Attribute Or Value Exists

  • Object Class Violation

  • Entry Already Exists

Long aborts

For HTTP, this is the number of operations manually stopped by the user by either clicking on the Stop or Refresh buttons or selecting another URL after at least 8 seconds of waiting for the page download (8 seconds is default). For XML, this is the number of transactions stopped after at least a threshold number of seconds of waiting (8 seconds is the default).

Long stopped pages

The number of operations manually stopped by the user by either clicking on the Stop or Refresh buttons or selecting another URL after at least 8 seconds of waiting for the page download (8 seconds is default). An operation is considered Stopped when its last HTTP request (the one that finished last) receives client's RESET packet before completion.

Loss rate in

This is the percentage of the number of total packets that were lost and needed to be retransmitted. Loss rate in refers to traffic to a server in a DataCenter configuration.

Loss rate out

This is the percentage of the number of total packets that were lost and needed to be retransmitted. Loss rate out refers to traffic from a server in a DataCenter configuration.

Mail server welcome msg. time

The time after which the server welcome message was received.

Max of server time thresholds

The maximum of used server time thresholds. If the server time is longer than the threshold, the operation is considered to be slow.

Max realized bandwidth threshold

Maximum realized bandwidth threshold.

Max slow operation threshold

The maximum of a slow operation threshold. If the operation time is longer than the threshold, the operation is considered to be slow.

Max Total bandwidth usage

The maximum value of Total bandwidth usage, over the time covered by the report.

Max Total packets/sec

The maximum value of Total packets/sec, over the time covered by the report.

Min of server time thresholds

The minimum of used server time thresholds. If the server time is longer than the threshold, the operation is considered to be slow.

Min realized bandwidth threshold

The acceptable transfer rate or throughput of server data when the transfer attempt occurred. If the monitored transfer rate falls below the specified threshold value, the operation is flagged as slow.

Min slow operation threshold

The minimum slow operation threshold.

MQ appl. errors

The number of all API errors for IBM WebSphere Message Queue. This metric is a sum of Message Queue application. errors (1) to (5).

MQ appl. errors (1)

The number of API errors of type 1 for IBM WebSphere Message Queue. Real User Monitoring distinguishes five types of API errors for IBM WebSphere Message Queue. The assignment of actual MQ return values to a particular error type number is configured on the AMD device, on per software service and per server basis. The error type numbers can then be mapped, on Central Analysis Server, onto named error categories. This is performed, on per-software service basis, on Message Queue reports.

MQ appl. errors (2)

The number of API errors of type 2 for IBM WebSphere Message Queue. Real User Monitoring distinguishes five types of API errors for IBM WebSphere Message Queue. The assignment of actual MQ return values to a particular error type number is configured on the AMD device, on per software service and per server basis. The error type numbers can then be mapped, on Central Analysis Server, onto named error categories. This is performed, on per-software service basis, on Message Queue reports.

MQ appl. errors (3)

The number of API errors of type 3 for IBM WebSphere Message Queue. Real User Monitoring distinguishes five types of API errors for IBM WebSphere Message Queue. The assignment of actual MQ return values to a particular error type number is configured on the AMD device, on per software service and per server basis. The error type numbers can then be mapped, on Central Analysis Server, onto named error categories. This is performed, on per-software service basis, on Message Queue reports.

MQ appl. errors (4)

The number of API errors of type 4 for IBM WebSphere Message Queue. Real User Monitoring distinguishes five types of API errors for IBM WebSphere Message Queue. The assignment of actual MQ return values to a particular error type number is configured on the AMD device, on per software service and per server basis. The error type numbers can then be mapped, on Central Analysis Server, onto named error categories. This is performed, on per-software service basis, on Message Queue reports.

MQ appl. errors (5)

The number of API errors of type 5 for IBM WebSphere Message Queue. Real User Monitoring distinguishes five types of API errors for IBM WebSphere Message Queue. The assignment of actual MQ return values to a particular error type number is configured on the AMD device, on per software service and per server basis. The error type numbers can then be mapped, on Central Analysis Server, onto named error categories. This is performed, on per-software service basis, on Message Queue reports.

MQ client errors

The number of IBM WebSphere Message Queue client errors. This includes the following Message Queue errors: ERR_NO_CHANNEL (value 0x01), ERR_CHANNEL_WRONG_TYPE (value 0x02), ERR_MSG_SEQUENCE_ERROR (value 0x04), ERR_USER_CLOSED (value 0x07), ERR_TIMEOUT_EXPIRED (value 0x08), ERR_TARGET_Q_UNKNOWN (value 0x09), ERR_BATCH_FAILURE (value 0x11).

MQ errors

The total number of IBM WebSphere Message Queue errors, including client errors, server errors, protocol errors and security errors.

MQ protocol errors

The number of IBM WebSphere Message Queue protocol errors. This includes the following Message Queue errors: ERR_PROTOCOL_SEGMENT_TYPE (value 0x0a), ERR_PROTOCOL_LENGTH_ERROR (value 0x0b), ERR_PROTOCOL_INVALID_DATA (value 0x0c), ERR_PROTOCOL_SEGMENT_ERROR (value 0x0d), ERR_PROTOCOL_ID_ERROR (value 0x0e), ERR_PROTOCOL_MSH_ERROR (value 0x0f), ERR_PROTOCOL_GENERAL (value 0x10), ERR_MESSAGE_LENGTH_ERROR (value 0x12), ERR_SEGMENT_NUMBER_ERROR (value 0x13), ERR_WRAP_VALUE_ERROR (value 0x15).

MQ security errors

The number of IBM WebSphere Message Queue security errors. This includes the following Message Queue errors: ERR_SECURITY_FAILURE (value 0x14), ERR_SSL_REMOTE_BAD_CIPHER (value 0x18).

MQ server errors

The number of IBM WebSphere Message Queue server errors. This includes the following Message Queue errors: ERR_QM_UNAVAILABLE (value 0x03), ERR_QM_TERMINATING (value 0x05), ERR_CAN_NOT_STORE (value 0x06), ERR_CHANNEL_UNAVAILABLE (value 0x16), ERR_TERMINATED_BY_REMOTE_EXIT (value 0x17).

MS Exchange errors

Total number of RPC Server and RPC Protocol errors. Counted only for MS Exchange analyzers.

Network performance

The percentage of total traffic that did not experience network-related problems (traffic in which the values of loss rate and RTT did not exceed configured thresholds).

Network performance affected bytes

The volume of TCP traffic that did experience network-related problems. The traffic measured here includes both directions of data transfer, to and from client, or downstream and upstream, but does NOT include bytes transferred internally within the site. By network-related problems we understand excessive RTT or Loss Rate: at any given moment, traffic is considered to be experiencing network-related problems if, at that particular time, the values of Loss Rate or RTT exceed pre-configured thresholds.

In situations when RTT measurements prove to be insufficient, ACK RTT may also become an additional criterion for determining network problems.

Network performance relevant bytes

The total volume of TCP traffic. Includes both directions of data transfer, to and from client, or downstream and upstream, but does NOT include bytes transferred internally within the site.

Network time

The time the network (between the user and the server) takes to deliver requests to the server and to deliver operation information back to the user. In other words, network time is the portion of the overall time that is due to the delivery time on the network.

Not-affected users (performance)

The percentage of users that did not experience application performance problems.

Now

Now

Number of e-mails

The number of e-mails detected during the reported period.

Number of e-mails per minute

The number of e-mails per minute.

Number of hits in an aborted operation

The number of hits in an aborted operation.

Operation (or network) throughput

The average aborted operation (or network) throughput in bytes per second.

Operation attributes

The number of operation attributes of all types (type 1 to 5), observed for the given software service.

Operation attributes (1)

The number of operation attributes of type 1, observed for the given software service.

Operation attributes (2)

The number of operation attributes of type 2, observed for the given software service.

Operation attributes (3)

The number of operation attributes of type 3, observed for the given software service.

Operation attributes (4)

The number of operation attributes of type 4, observed for the given software service.

Operation attributes (5)

The number of operation attributes of type 5, observed for the given software service.

Operation length

The number of packets that contained in an average operation.

Operation percentage breakdown

Operation percentage breakdown into slow and fast operations.

Operations

The number of operations. The term "operations" refers to operations in the context of the particular protocol, and can mean HTTP/HTTPS page loads, database queries, XML (transactional services) operations, Jolt transactions on a Tuxedo server, e-mails, DNS requests, Oracle Forms submissions, MQ operations, VoIP calls, MS Exchange operations, or SAP operations.

Operations/min

The number of operations per minute.

Operations/sec

The number of operations per second.

Operations breakdown

Operation breakdown into numbers of slow and fast operations.

Operation size

The average operation size expressed in bytes.

Operations per minute

The number of operations per minute.

Operations with breakdown

The number of operations with operation breakdown into numbers of slow and fast operations.

Operations with large server time

The number of operations for which the server time was above a predefined threshold value.

Operation time

The time it took to complete an operation. The term "operation" refers to an operation in the context of a particular protocol, and can mean HTTP/HTTPS page loads, database queries, XML (transactional services) operations, Jolt transactions on a Tuxedo server, e-mails, DNS requests, Oracle Forms submissions, MQ operations, VoIP calls, MS Exchange operations, or SAP operations. Note that an operation can be split over several packets. For HTTP and HTTPS, it is equal to the redirect time plus the network time plus server HTTP time plus server think time.

Operation time breakdown

Operation time breakdown into the server time, the network time, the redirect time, and the other time.

Operation time percentage breakdown

The breakdown of the average value of operation time into percentage of the server time, the network time, the redirect time, and the other time.

Operation time with breakdown

The time it took to complete an operation with an operation time breakdown into the server time, the network time, the idle time, and the other time.

Oracle Applications error

The number of Oracle Application errors that occurred during a given operation. For a complete list of specific Forms server errors, refer to the RUM Console Help.

Oracle Forms errors

The number of Oracle Forms errors that occurred during a given operation. For a complete list of specific Forms server errors, refer to the RUM Console Help.

Oracle server error

The number of Oracle server errors that occurred during a given operation. For a complete list of specific Forms server errors, refer to the RUM Console Help.

Orphaned redirects

The number of HTTP redirects for which a matching request to the target URL was not detected before the timeout time.

Other SSL errors (default name)

SSL alerts other than those for SSL errors 1 and SSL errors 2.

Other time

Part of the operation time, calculated as Operation time - Server Time - Network Time - Idle time. For RUM sequence transactions, the other time is sum of the client response time and the application processing time.

Out of contract bytes

The number of bytes marked as Out-of-contract in the TOS field in the TCP header. This setting can signify that the data was sent over and above a certain preset limit.

Out of contract packets

The number of packets marked as Out-of-contractin the TOS field in the TCP header. This can signify that the data was sent over and above a certain preset limit.

Page breakdown

Operation breakdown into numbers of slow and fast operations.

Page load time

The total operation time as perceived by the user. This includes redirect time.

Page load time breakdown

The breakdown of total operation time, as perceived by the user, into redirect time, server think time, server time and network time.

Page load time percentage breakdown

The breakdown of total operation time, as perceived by the user, into percentages of redirect time, server think time, server time and network time.

Page percentage breakdown

Operation percentage breakdown into slow and fast operations.

Page requests breakdown

The breakdown of operation requests into fast operations, slow operations and operations stopped.

Page requests percentage breakdown

The percentage breakdown of operation requests into fast operations, slow operations and operations stopped.

Pages

The number of Web pages loaded.

Page size

The operation size expressed in bytes.

Pages per minute

The number of operations per minute.

Pages stopped

The number of operations manually stopped by the user by either clicking on the Stop or Refresh buttons, or by selecting another URL.

Pages with large server time

The number of operations with server time that exceeded the predefined threshold.

Pages with large server time per minute

The number of operations with server time that exceeded the predefined threshold, per minute.

Pages with small server time

Operations for which the server time was below the predefined threshold.

Peak

Peak

Percentage of aborts

The percentage of transactions aborted by the client. It applies to all TCP-based protocols. For example, for HTTP, it is the number of operations manually stopped by the user by either clicking the Stop or Refresh buttons or selecting another URL. Note that, in the case of HTTP, this number includes Short aborts and Long aborts.

Percentage of affected clients (application)

The percentage of clients that experienced application performance problems.

Percentage of affected clients (availability)

The percentage of clients that were affected by the availability related problems.

Percentage of affected clients (network)

The number of unique clients that experienced network performance problems.

Percentage of affected users (availability)

The percentage of users that were affected by the availability related problems.

Percentage of affected users (availability) breakdown

A percentage breakdown of users into how many were affected by availability problems and how many were not.

Percentage of affected users (network)

The percentage of unique users that experienced network performance problems.

Percentage of affected users (network) breakdown

A percentage breakdown of users into how many were affected by network performance problems and how many were not.

Percentage of affected users (performance)

The percentage of users that experienced application performance problems.

Percentage of affected users (performance) breakdown

A percentage breakdown of users into how many were affected by application performance problems and how many were not.

Percentage of long aborts

The percentage of HTTP operations manually stopped, by the user by either clicking on the Stop or Refresh buttons or selecting another URL, after significant time of waiting for the page download. The default wait time duration, classifying an abort as long, is 8 seconds. This threshold value is configurable. The same threshold value is also used to determine if an HTTP page was slow to load. Note that this metric applies exclusively to HTTP.

Percentage of network time

The network part of the transaction time, expressed as percentage.

Percentage of optimized traffic (bytes)

Indicates the traffic distribution in two separate branches: optimized traffic and passed-through traffic.

The higher the value, the more bytes are optimized.

Low values may indicate poorly configured optimization or optimization device overload.

Percentage of optimized traffic (packets)

Indicates the traffic distribution in two separate branches: optimized traffic and passed-through traffic. The higher the value, the more packets are optimized. Low values may indicate poorly configured optimization or optimization device overload.

Percentage of pages with large server time

The percentage of operations with server time that exceeded the predefined threshold.

Percentage of short aborts

The percentage of HTTP operations manually stopped, by the user by either clicking on the Stop or Refresh buttons or selecting another URL, before significant time of waiting for the page download. The default wait time duration, classifying an abort as long, is 8 seconds. This threshold value is configurable. The same threshold value is also used to determine if an HTTP page was slow to load. Note that this metric applies exclusively to HTTP.

Percentage of slow form submissions

The percentage of Oracle Forms submissions qualified as slow.

Percentage of slow operations

The percentage of operations for which the operation time was above a predefined threshold value. The term "operations" refers to operations in the context of the particular protocol, and can mean HTTP/HTTPS page loads, database queries, XML (transactional services) operations, Jolt transactions on a Tuxedo server, e-mails, DNS requests, Oracle Forms submissions, MQ operations, VoIP calls, MS Exchange operations, or SAP operations.

Percentage of slow pages

The percentage of slow operations due to the given reason.

Percentage of slow queries

The percentage of database queries qualified as slow.

Percentage of slow requests

The percentage of requests with the value of request time exceeding the predefined threshold.

Percentage of slow responses

The percentage indicating the number of slow server responses.

Percentage of stopped pages

The percentage of operations manually stopped by the user by either clicking on the Stop or Refresh buttons or selecting another URL.

Percentage of TCP sessions w/errors

The percentage of TCP sessions with errors.

Performance

Depending on the particular tier, the term performance can mean:

  • For Client tiers: the percentage of transactions completed in a time shorter than the defined time threshold, calculated as 100-100*(slow transactions/all transactions).

  • For the Client optimized network tier: the percentage of compressed bytes.

  • For other Network tiers: the percentage of total traffic that did not experience network-related problems.

  • For Data center tiers: for transactional protocols, this is the percentage of software service operations completed in a time shorter than the performance threshold. For transactionless, TCP-based protocols, this is the percentage of monitoring intervals in which user wait time per kB of data was shorter than the threshold value.

Person-hours lost

In Central Analysis Server, the total monitoring time clients waited for operations due to bad service availability and bad application performance In Advanced Diagnostics Server, the total time clients waited for operations due to bad software service performance, that is, the total monitoring time during which operation time exceeded the predefined threshold. Note that this is not a sum of whole monitoring intervals, but only those intervals' portions during which problems occurred. This metric is not calculated in PVU mode.

Person-hours lost (availability)

The total time clients waited for operations due to bad service availability, that is, the total monitoring time during which attempts were made to connect to a server and these attempts were not successful - no connection was established.

Person-hours lost (errors)

The total time during which clients waited for operations to load due to application errors. Note that it refers only to operations detected by the following analyzers: HTTP, SSL and SSL Decrypted. This metric is not calculated in PVU mode.

Person-hours lost (performance)

The total time clients waited for operations to load due to bad software service performance, that is, the total monitoring time during which transaction time exceeded the predefined threshold. Note that this is not a sum of whole monitoring intervals, but only those intervals' portions during which problems occurred. This metric is not calculated in PVU mode.

Primary Reason for Slowness

Primary reason for slowness is one of the general categories causing operations to be slow. The categories include data center, network, application design, client/3rd party, and multiple reasons.

Primary Reason for Slowness details

The details of the primary reason for slowness.

Queries

The number of database queries detected during the reported period.

Queries per minute

The number of database queries per minute.

Query breakdown

Query breakdown into numbers of slow and fast queries.

Query percentage breakdown

Query percentage breakdown into slow and fast queries.

Query result size

The query size expressed in bytes.

Query time

The average value of the time it took to execute a query.

Query time breakdown

The average value of the query time breakdown into server time and network time.

Query time percentage breakdown

The average value of the query time breakdown into percentages of server time and network time.

Redirect time

The average amount of time that was spent between the time when a user went to a particular URL and the time this user was redirected to another URL and issued a request to that new URL. The difference between Redirect Time and HTTP Redirect Time is that the former counts all operations, while the latter refers only to those operations for which redirection actually took place.

Request/Response size

The number of bytes sent by the server in response to a DNS request.

Request breakdown

The breakdown of DNS requests into slow and fast requests.

Request percentage breakdown

The percentage breakdown of DNS requests into slow and fast requests.

Requests

The number of all operation requests, both requests that became successful operations and requests that were aborted by the client.

Requests breakdown

The number of operation or transaction requests with operation or transaction breakdown into numbers of slow, fast, aborted, and failed operations or transactions.

Requests breakdown (with tooltip)

Operation or transaction breakdown into numbers of slow, fast, aborted, and failed operations or transactions.

Requests percentage breakdown (with tooltip)

Operation or transaction percentage breakdown into slow, fast, aborted, and failed operations or transactions.

Requests per minute

The number of DNS requests per minute.

Request time

The time it took the client to send the HTTP request to the server (for example, by means of an HTTP GET or HTTP POST). Note: This time includes TCP connection setup time and SSL session setup time (if any). It starts when the client starts the TCP session on the server and ends when the server receives the whole request. Sometimes an operation is slow because of a big request rather than due to a large response.

Response messages

The total number of protocol-specific server responses. That includes both errors and other identifiable response strings, as configured in monitoring.

Responses

The number of DNS responses during the reported period.

Responses per minute

The number of DNS responses per minute.

Response time

The average response time from the DNS server.

Response transfer time

The time it took the server to send the response to the client (for example, by means of an HTTP GET or HTTP POST). The value is obtained by subtracting Server Time and Request Time from Operation Time.

RMI/Universal decode error (1)

The number of RMI/Universa Decode errors of category 1.

RMI/Universal decode error (2)

The number of RMI/Universal Decode errors of category 2.

RMI/Universal decode error (3)

The number of RMI/Universal Decode errors of category 3.

RMI/Universal decode error (4)

The number of RMI/Universal Decode errors of category 4.

RMI/Universal decode error (5)

The number of RMI/Universal Decode errors of category 51.

RMI/Universal decode error (6)

The number of RMI/Universal Decode errors of category 6.

RMI/Universal decode error (7)

The number of RMI/Universal Decode errors of category 7.

RMI/Universal decode errors

Total number of RMI/Universal Decode errors.

RPC Client error

---- RPC Client error

RPC errors

Total number of RPC server, RPC security and RPC protocol errors. Counted only for RPC analyzer.

RPC Protocol error

The number of all RPC_X_* errors.

RPC Security error

---- RPC Security error

RPC Server error

The number of all RPC_S_* and EPT_S_* errors.

RTT measurements

The number of RTT measurements. An RTT measurement occurs during every TCP handshake, so it provides some insight into the number of attempted TCP sessions, and the potential accuracy of the RTT measurements that are reported.

Sampling rate

The total percentage of packets that the AMD was able to process. Numbers lower that 100% mean that a portion of packets had been dropped because of performance issues.

Sampling means dropping packets when network interface driver performance is degraded on the AMD. Packets are dropped in a controlled manner and always with care to preserve complete and therefore consistent sessions.

SAP GUI error indicator

Errors detected by examining the error strings returned to the user in Window Status or other SAP GUI data. Detected errors are included in availability calculation for the SAP application.

SAP GUI errors

The number of errors detected on the protocol level in communication between SAP application server and SAP GUI client as well as between SAP application server and a third party clients using Remote Function Calls (RFC).

SAP GUI status error

This automatically created group, consists values based on default configuration of patterns for Application Responses for the most commonly used errors.

SAP RFC error

An error consisting values based on user-defined configuration of patterns for Application Responses for the most common errors that are traced in selected fields in the SAP RFC protocol.

SAP RFC error indicator

Errors detected by examining the error strings returned in the user-defined attributes that are traced in selected fields in the SAP RFC protocol. Detected errors are included in the availability calculation for the SAP application.

SAP RFC errors

The number of errors detected on the protocol level in communication between a SAP application server and a SAP client plus the number of attributes which are defined as error indicators in the monitoring configuration.

Server ACK RTT

RTT measurement performed during ACK packet transmission, from server side of the operation. Also provided are minimum, maximum and standard deviation values.

Server ACK RTT measurements

These metrics keep track of how many RTT of Server ACK measurements were made. ACK measurement is performed during ACK packet transmission either from server or client side of the transaction.

Server bandwidth usage

The number of server bits per second.

Server bytes

The number of bytes sent by servers. The number includes headers.

Server loss rate

The percentage of total packets sent from a server that were lost and needed to be retransmitted.

Server loss rate (AMD to client)

The percentage of total packets sent by a server that were lost - between the AMD and the client - and needed to be retransmitted.

Server loss rate (server to AMD)

The percentage of total packets sent by a server that were lost - between the AMD and the server - and needed to be retransmitted.

Server not responding errors

The number of Server Not Responding errors. This category of errors applies when the client closes the TCP session with a RESET packet after the server has failed to respond for too long.

Server operations

The number of operations (for HTTP/SSL this is equivalent to the number of pages, for DB/2 it is equivalent to the number of queries) from the server side. For traffic analyzed with the analyzers General-volume and ICA (Citrix), this is the number of server data transfers for which network realized bandwidth was measured.

Server operation size

The size of a server operation. In HTTP and HTTPS (decrypted and non-decrypted), server operation size equals the operation size.

Server packets

The number of packets sent by the servers.

Server packets/sec

The number of packets per second, sent by the servers.

Server packet size

The average size of the server-originating packets (in bytes), including header.

Server packets lost (AMD to client)

The number of packets sent by a server that were lost - between the AMD and the client - and needed to be retransmitted.

Server packets lost (server to AMD)

The number packets sent by a server that were lost - between the server and the AMD - and needed to be retransmitted.

Server realized bandwidth

Server realized bandwidth refers to the actual transfer rate of server data when the transfer attempt occurred, and takes into account factors such as loss rate (retransmissions). Thus, it is the size of an actual transfer divided by the transfer time.

Server response time

This is the amount of time it takes for a server to provide its initial response to a user's operation request. Often servers will respond with some information quickly, before all the information is ready for delivery. Together with the server think time, the server response time sums to the overall server time. Note that if there was no think time recorded for the opration, it equals the server time.

Server retransmission timeouts

Number of times retransmission timeout occurred on server connection. Calculated only for AppFlow records collected by AMD from NetScaler.

Server RTT

The time it takes for a SYN packet (sent by a user) to travel from the AMD to a monitored server and back again. Also provided are minimum, maximum and standard deviation values.

graphical illustration

Server session termination errors

The number of Server Session Termination errors. This category of errors applies when the server detects an error on the software service level and closes the TCP session with a RESET packet.

Server TCP data packets

The total number of TCP packets sent by the servers, excluding the traffic control packets.

Server TCP data packets lost

The number of lost TCP data packets sent by the servers, excluding the traffic control packets. The number of lost TCP packets always regards the context of the counter, for example, an application, a client or any other entity.

Server think time

The time that elapsed between the moment the server received the request for the Base Page, and the time the server fully composed the response. Depending on the nature of the request, Application Servers in the Data Center may be involved to produce the content. In such a case, this additional time will be reflected in the Server Think Time metric.

Server time

The time it took the server to produce a response for the given request.

Server time breakdown

Server time breakdown into number of operations with large server time and operations with small server time.

Server time percentage breakdown

Server time percentage breakdown into operations with large server time and operations with small server time.

Short aborts

The number of transactions stopped before timeout. For HTTP, this is the number of page loads software service manually stopped by the user by either clicking on the Stop or Refresh buttons or selecting another URL before 8 seconds of waiting for the page download (8 seconds is default). For XML, this is the number of transactions stopped before a threshold number of seconds of waiting (8 seconds is the default).

Short stopped pages

The number of operations manually stopped by the user by either clicking on the Stop or Refresh buttons or selecting another URL before 8 seconds of waiting for the page download (8 seconds by default). An operation is considered Stopped when its last HTTP request (the one that finished last) receives client's RESET packet before completion.

Slow form submissions

The number of Oracle Forms submissions qualified as slow.

Slow form submissions per minute

The number of slow form submissions per minute.

Slow operations

The number of operations for which the operation time was above a predefined threshold value. The term "operations" refers to operations in the context of the particular protocol, and can mean HTTP/HTTPS page loads, database queries, XML (transactional services) operations, Jolt transactions on a Tuxedo server, e-mails, DNS requests, Oracle Forms submissions, MQ operations, VoIP calls, MS Exchange operations, or SAP operations. Note that slow operations for SMB are not determined using the time threshold, but maximum and minimum realized bandwidth thresholds.

Slow operations (application design)

The number of slow operations caused by the application design category as calculated using the primary reason for slowness algorithm. Note that this includes only sucessful operations. Failures and aborted operations are not taken into account.

Slow operations (application design - # of components)

The number of slow operations caused by the number of components, which is one of the detailed reasons in the application design category as calculated using the primary reason for slowness algorithm. Note that this includes only sucessful operations. Failures and aborted operations are not taken into account.

Slow operations (application design - redirect time)

The number of slow operations caused by redirect time, which is one of the detailed reasons in the application design category as calculated using the primary reason for slowness algorithm. Note that this includes only sucessful operations. Failures and aborted operations are not taken into account.

Slow operations (application design - request size)

The number of slow operations caused by request size, which is one of the detailed reasons in the application design category as calculated using the primary reason for slowness algorithm. Note that this includes only sucessful operations. Failures and aborted operations are not taken into account.

Slow operations (application design - response size)

The number of slow operations caused by response size, which is one of the detailed reasons in the application design category as calculated using the primary reason for slowness algorithm. Note that this includes only sucessful operations. Failures and aborted operations are not taken into account.

Slow operations (client/3rd party)

The number of slow operations caused by client/3rd party category as calculated using the primary reason for slowness algorithm. Note that this includes only sucessful operations. Failures and aborted operations are not taken into account.

Slow operations (data center)

The number of slow operations caused by the data center category as calculated using the primary reason for slowness algorithm. Note that this includes only sucessful operations. Failures and aborted operations are not taken into account.

Slow operations (multiple reasons)

The number of slow operations caused by multiple reasons, that is when the algorithm was not able to determine one primary reason for slowness. Note that this includes only sucessful operations. Failures and aborted operations are not taken into account.

Slow operations (network)

The number of slow operations caused by the network category as calculated using the primary reason for slowness algorithm. Note that this includes only sucessful operations. Failures and aborted operations are not taken into account.

Slow operations (network - latency)

The number of slow operations caused by latency, which is one of the detailed reasons in the network category as calculated using the primary reason for slowness algorithm. Note that this includes only sucessful operations. Failures and aborted operations are not taken into account.

Slow operations (network - loss rate)

The number of slow operations caused by loss rate, which is one of the detailed reasons in the network category as calculated using the primary reason for slowness algorithm. Note that this includes only sucessful operations. Failures and aborted operations are not taken into account.

Slow operations (network - other)

The number of slow operations caused by other factors than latency or loss rate, which is one of the detailed reasons in the network category as calculated using the primary reason for slowness algorithm. Note that this includes only sucessful operations. Failures and aborted operations are not taken into account.

Slow operations per minute

The number of operations for which the operation time was above a predefined threshold value, per minute. The term "operations" refers to operations in the context of the particular protocol, and can mean HTTP/HTTPS page loads, database queries, XML (transactional services) operations, Jolt transactions on a Tuxedo server, e-mails, DNS requests, Oracle Forms submissions, MQ operations, VoIP calls, MS Exchange operations, or SAP operations.

Slow pages

The number of slow operations due to the given reason.

Slow pages per minute

The number of slow operations due to the given reason.

Slow queries

The number of database queries qualified as slow.

Slow queries per minute

The number of database queries qualified as slow, per minute.

Slow requests

The number of requests for which the request time was above a predefined threshold value.

Slow requests per minute

The number of requests with request time exceeding the predefined threshold, per minute.

Slow responses

The number of slow server DNS responses.

Slow responses per minute

The number of slow DNS responses per minute.

Slow user sessions

The number of client sessions, which contained at least one slow operations (page load for HTTP or HTTPS).

SMTP command syntax error (default name)

The number of "SMTP command syntax" errors, that is server response code numbers between 500 and 504. These values are default and can be customized.

SMTP errors

The total number of SMTP errors.

SMTP general system error (default name)

The number of "SMTP general system" errors, that is server response code numbers 421, 451, 452 or 554. These values are default and can be customized.

SMTP mailbox not available (default name)

The number of "SMTP mailbox not available" errors, that is server response code numbers 450, 550, 551, 552, 553. These values are default and can be customized.

SSL conn. setup per operation

The time it took to establish an SSL connection between the client and the server, weighted per number of operations. For HTTP-based software services, a single operation means a single page.

SSL conn. setup per session

The time it took to establish an SSL connection between the client and the server.

SSL errors

The number of all SSL alerts. This metric is the sum of SSL Session Fatal Errors, SSL Handshake Errors and SSL Warnings.

SSL errors 1 (default name)

If not explicitly configured, general SSL alerts from the following list: 10,20,21,22,30,40,49,50,51.

SSL errors 2 (default name)

If not explicitly configured, general SSL alerts from the following list: 41,42,43,44,45,46,48.

SSL handshakes

The number of observed SSL handshakes.

Standalone hits

The number of hits not associated with any operation, such as orphaned redirects, unauthorized hits, and discarded hits (no server response).

Status

Status

Stopped pages breakdown

The breakdown of all stopped operations into numbers of slow and fast stopped operations.

Stopped pages percentage breakdown

The breakdown of stopped operations into percentages of slow and fast stopped operations.

Successful attempts

The number of monitoring intervals during which successful attempts were made to connect to a server. Note that this is counted separately for each server. Thus, if in a given monitoring interval there are attempts to connect to three different servers, the Successful attempts metric will be incremented by three for that one monitoring interval. Note also that, even if TCP errors occur, but the connection is established during the given monitoring interval, then this monitoring interval is counted as a success (for that server).

Successful attempts (transport)

The difference between the total number of operations and the number of operations with errors.

Successfully closed sessions

The number of sessions that have been active for at least a period of time equal to predefined time-out time (by default 5 minutes), and did not encounter any TCP errors.

Successful TCP connection attempts

The number of successful TCP connection attempts.

Sum of failures and response messages

Sum of failures and response messages.

TCP + MS Exchange errors

Total number of TCP errors, RPC Server and RPC Protocol errors.

TCP connections attempts

The number of all TCP connection attempts (successful and unsuccessful).

TCP errors

The total number of TCP errors.

Those errors may indicate server or application problems and therefore measurements of those are critical to understanding the issues that may affect end-user experience. AMDs measure and report on the following types of TCP errors:

  • Connection Refused Errors - Client attempts to open a TCP session with a server, which rejects the request. SYN packet from Client is followed by RESET packet from Server, with matching TCP sequence numbers. This error is typically caused by resource exhaustion on the server, which is unable to accept more concurrent TCP sessions. This may be either a configuration issue (too few resources allocated in the kernel) or lack of memory. SYN flood attacks typically result in servers being unable to accept new connections.

  • Server session termination error - Server is unexpectedly terminating a connection that was successfully opened. The server sends a RESET packet to the Client. Such an error originates at an application using TCP session that is monitored. It does not necessarily mean application failure; usually it means that the application encountered a condition in which it decided to immediately terminate session with the client, for example, because of an application security policy violation by the client.

  • Session Abort - Client is unexpectedly terminating a connection that was successfully opened. The Client sends a RESET packet to the Server. These errors are inspected in the context of the client application and may or may not be reported. For example, the browser running HTTP may terminate the load of a GIF file if it is older than the one that it had previously cached and this is normal behavior. However, if all connections to the server are terminated because the user hits the STOP button, then this is abnormal session termination and is reported as "Aborted operation" or "Stopped Page".

  • Client not responding errors (server timeout errors) - Server networking stack takes an assumption that the network connection to the client exists, but the client remains idle and does not respond. In such a case, the server closes the TCP session with the RESET packet. Such a condition may occur when the client has been silently disconnected from the network, for example, due to a link failure, or the client has crashed. Note that this error will not occur if the client has ended the session gracefully, e.g. by closing the client application.

  • Server not responding errors (client timeout errors) - Client networking stack takes an assumption that network connection to the server exists, but the server remains idle and does not respond. In such a case, the client closes the TCP session with the RESET packet. This may occur either during the Session Setup phase (no response to the SYN packet), or during a normal data exchange process. Such a situation may result in the intermittent network problems between the client and the server. In the case the traffic is routed through asymmetric paths across the Internet, which is often the case, the path from the server to the client may be broken.

TCP sessions

The total number of opened TCP connections.

TCP SYN time

The time needed to establish a connection on the TCP/IP layer, that is, the average time it took to transfer SYN packets.

Throughput

Throughput

Time resolution

The value of the time resolution for the given report. While being of constant value for a particular report, this metric will be present or absent, for different values of the time dimension, thus showing user activity in time. It can also provide useful information when compared - on the same graph - with aggregate time metrics.

Time to abort

The average aborted operation duration including the redirect time. In the case of HTTP and SSL, this is the operation time.

Today

Today

Total bandwidth usage

The number of all transmitted bits (client + server) per second.

Total bandwidth usage with breakdown

Total bandwidth usage (client + server) with breakdown into client and server bandwidth usage.

Total bytes

The number of all transmitted bytes (client + server).

Total bytes compression

The data optimization observed, expressed as a byte reduction and a percentage, where a lower byte count on the WAN side means a higher reduction:

  • 0% for pass-through.

  • Less than 0% if more bytes were observed on the WAN side, including both pass-through and optimized traffic.

  • Greater than 0% if fewer bytes were observed on the WAN side, including both pass-through and optimized traffic.

This metric should not exceed 100%.

Total bytes on LAN side

The sum of bytes (client's and server's) observed on the LAN side before network traffic is directed into the WAN Optimization Controller (WOC).

Total bytes on WAN side

The sum of bytes (client's and server's) observed on the WAN side after network traffic leaves the WAN Optimization Controller (WOC), including bytes that have been passed through and those that have been marked as optimized.

Total packets

The number of all transmitted packets (client + server).

Total packets/sec

The number of all transmitted packets (client + server) per second.

Total packets compression

The data optimization observed, expressed as a packet count reduction and a percentage, where a lower the packet count on the WAN side means a higher reduction:

  • 0% for pass-through.

  • Less than 0% if more packets were observed on the WAN side, including both pass-through and optimized traffic.

  • Greater than 0% if fewer packets were observed on the WAN side, including both pass-through and optimized traffic.

This metric should not exceed 100%.

Total packets on LAN side

The sum of packets (client's and server's) observed on the LAN side before network traffic is directed into the WAN Optimization Controller (WOC).

Total packets on WAN side

The sum of packets (client's and server's) observed on the WAN side after network traffic leaves the WAN Optimization Controller (WOC), including packets that have been passed through and those that have been marked as optimized.

Total wait time

The total time of all transactions.

Transact. errors

The number of transaction errors (applies to Jolt (Tuxedo)).

Transact. rollbacks

The number of transaction rollbacks (applies to Jolt (Tuxedo)).

Transact. rollbacks after timeout

The number of transaction rollbacks that occurred after a predefined timeout (applies to Jolt (Tuxedo)).

Transact. rollbacks before timeout

The number of transaction rollbacks that occurred before a predefined timeout (applies to Jolt (Tuxedo)).

Transact. service authentication errors

The number of "service transaction authentication" errors (applies to Jolt (Tuxedo)).

Transact. service not found errors

The number of "transaction service not found" errors (applies to Jolt (Tuxedo)).

Transactional service errors

The total number of transactional service errors.

Transfer time

The average time it took the server to send a response to the client, averaged over all the operations in the monitoring interval.

Transport errors

The number of transport related errors.

Turns

On Transactional Services Status reports, the number of subcomponents of error-free operations.

Turns per operation

On Transactional Services Status reports, the number of turns per operation.

Two-way loss rate

The percentage of total packets (client and server) that were lost (due to network congestion, low router queue capacity or other reasons) and needed to be retransmitted.

Unavailability (total)

This is the difference between 100% and availability.

Unavailability (transport)

(Application failures/Application successful attempts)*100%.

Unique and affected users (availability)

The number of unique users with a breakdown of users into how many were affected by availability problems and how many were not.

Unique and affected users (availability) (1)

A breakdown showing how many unique users were affected by availability problems.

Unique and affected users (availability) (2)

The number of unique users with a breakdown showing how many users were affected by availability problems.

Unique and affected users (network)

The number of unique users with a breakdown of users into how many were affected by network performance problems and how many were not.

Unique and affected users (network) (1)

A breakdown showing how many unique users were affected by network performance problems.

Unique and affected users (network) (2)

The number of unique users with a breakdown showing how many users were affected by network performance problems.

Unique and affected users (performance)

The number of unique users with a breakdown of users into how many were affected by application performance problems and how many were not.

Unique and affected users (performance) (1)

A breakdown showing how many unique users were affected by application performance problems.

Unique and affected users (performance) (2)

The number of unique users with a breakdown showing how many users were affected by application performance problems.

Unique client groups

The number of unique client groups, to which the detected clients belong.

Unique client IP addresses

The number of unique IP addresses of the clients. When clients are aggregated to so-called aggregation blocks, only the most active IP addresses per reported entity are kept in the database. However, the extended ISP mode enables you to count user IP addresses that are aggregated as single users.

Unique clients

The number of unique clients, detected in the monitored traffic.

Unique internal client IP addresses

The number of unique client IP addresses, as seen in their local networks. When clients are aggregated to so-called aggregation blocks, only the most active IP addresses per reported entity are kept in the database. However, the extended ISP mode enables you to count user IP addresses that are aggregated as single users.

Unique operations

The number of different operations (queries, operation types, etc.).

Unique servers

The number of unique servers, that is, unique server IP addresses.

Unique services

The number of unique services. A unique service is defined by a software service name, agent name (for synthetic traffic), analyzer name, server IP address, server name, and Type of Service value.

Unique sites

The number of unique client sites.

Unique timestamps

The number of the unique time stamps used to sign the traffic performance data packages.

Unique users

The number of unique users detected in the monitored traffic.

Unique users and percentage of affected users (availability)

The number of unique users with a percentage breakdown showing how many users were affected by availability problems.

Unique users and percentage of affected users (network)

The number of unique users with a percentage breakdown showing how many users were affected by network performance problems.

Unique users and percentage of affected users (performance)

The number of unique users with a percentage breakdown showing how many users were affected by application performance problems.

User sessions

The number of user HTTP sessions. The count can be identified by information contained in intercepted HTTP cookies or by HTTP authorization.

User wait time per kB

Reversed throughput, that is the average time spent by the user waiting for delivery of 1 kB of software service data (operations time vs. operation size).

VoIP delay

VoIP average networking delay, as reported by Real Time Transport Protocol (RTCP), measured for both downstream and upstream traffic.

VoIP delay for client-to-server traffic

VoIP average networking delay in the upstream direction, that is, from a local to a remote VoIP endpoint.

VoIP delay for server-to-client traffic

VoIP average networking delay in the downstream direction, that is, from a remote to the local VoIP endpoint.

VoIP Jitter

VoIP average jitter measured by the probe, for both downstream and upstream traffic. Jitter is a variation in voice data transit delay, in milliseconds. In general, higher levels of jitter are more likely to occur on either slow or heavily congested links.

VoIP Jitter for client-to-server traffic

VoIP average jitter as reported by Real Time Transport Protocol (RTCP), for upstream traffic. Jitter is a variation in voice data transit delay, in milliseconds. Higher levels of jitter are more likely to occur on either slow or heavily congested links.

VoIP Jitter for server-to-client traffic

VoIP average jitter measured by the probe in the downstream traffic, that is, from a remote VoIP phone to the local endpoint. Jitter is a variation in voice data transit delay, in milliseconds.

VoIP loss rate

The percentage of VoIP packets lost or discarded that needed to be retransmitted, measured for both upstream and downstream traffic.

VoIP loss rate for client-to-server traffic

The percentage of VoIP packets lost or discarded that needed to be retransmitted, measured for upstream traffic.

VoIP loss rate for server-to-client traffic

The percentage of VoIP packets lost or discarded that needed to be retransmitted, measured for downstream traffic.

VoIP MOS

VoIP average Mean Opinion Score (MOS) rating of the call quality, for both downstream and upstream traffic.

VoIP MOS for client-to-server traffic

VoIP average Mean Opinion Score (MOS) measured in the upstream direction, that is, from a subscriber to a remote VoIP phone.

VoIP MOS for server-to-client traffic

VoIP average Mean Opinion Score (MOS) measured in the downstream direction, that is, from a remote VoIP phone to the subscriber.

VoIP R-factor

VoIP average R-factor value, for both downstream and upstream traffic. It is a transmission quality rating, with a typical range of 50-100. An R-Factor score is derived from multiple VoIP metrics, including latency, jitter, and loss.

VoIP R-factor for client-to-server traffic

VoIP average R-factor value in the upstream direction, that is, from a subscriber to a remote VoIP phone.

VoIP R-factor for server-to-client traffic

VoIP average R-factor value in the downstream direction, that is, from a remote VoIP phone to the subscriber.

VoIP RTCP Jitter

VoIP average jitter as reported by Real Time Transport Protocol (RTCP), for both downstream and upstream traffic. Jitter is a variation in voice data transit delay, in milliseconds. Higher levels of jitter are more likely to occur on either slow or heavily congested links.

VoIP RTCP Jitter for client-to-server traffic

VoIP average jitter as reported by Real Time Transport Protocol (RTCP) for the upstream traffic, that is, from a local VoIP endpoint to a remote one. Jitter reflects a variation in voice data transit delay, expressed in milliseconds.

VoIP RTCP Jitter for server-to-client traffic

VoIP average jitter as reported by Real Time Transport Protocol (RTCP) for the downstream traffic, that is, from a remote VoIP endpoint to the local endpoint. Jitter reflects a variation in voice data transit delay, in milliseconds.

Web errors

The total number of all HTTP errors, both client and server errors.

Window title

SAP GUI decode has an option to retrieve form field values from selected SAP form fields. This automatically created group, aggregates metrics related to errors based on window title.

Zero window size events (client)

Client sets this in TCP header when it wants the other side to slow down with data transmission because it cannot keep up with the transmission speed. Indicates that receiving machine is busy with other tasks.

Zero window size events (server)

Zero window size events (server)

 

  • No labels