Data Center RUM Documentation

Skip to end of metadata
Go to start of metadata

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

Synthetic and sequence transaction data dimensions

AMD UUID (id: traceAmdUUID)

UUID (Universal Unique Identifier) of the AMD that produced the data.

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, used for linking purposes.

Application (id: bgAppl)

A universal container that can accommodate transactions.

Application Monitoring Correlation ID (id: vaGUID)

Java and .NET Monitoring GUID

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.

Citrix server (id: citrixServer)

The IP address of the Citrix server.

Citrix server IP (id: transCitrixServerIP)

The IP address of a Citrix server.

Client area (id: cLocArea)

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, 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.

Client country (id: cGeoCountry)

Geographical data about the client country.

Client geographical region (id: cGeoRegion)

Geographical data about the client region.

Client group (id: userNGr)

The client's group, as manually defined in Central Analysis Server.

Client identifier (id: cIdentifier)

Client identifier

Client identifier type (id: cIDType)

internalId: cIDType

descriptionTmxId: RTM_DV_TRANS_HELP_DIMENSION_cIDType

!!! FIXME Description missing in TMX !!!

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.

Client name (id: clientN)

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

Client region (id: cRegion)

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.

Client site (id: cLoc)

Sites, areas, and regions define a logical grouping of clients and servers 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.

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. 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, used for report linking purposes.

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 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)

The 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.

Dynatrace Network Analyzer GUID (id: avGUID)

The number identifying a Synthetic Monitoring transaction.

Dynatrace Network Analyzer link status (id: avLinkStatus)

An indicator of the Transaction Trace report availability. When a problem occurs, for example, a transaction is too slow, and the Transaction Trace file contains such information, a full Transaction Trace report may be requested directly from the CAS.

The indicator has three states:

  • The report can be generated (Click to generate report)

  • The report has been requested (Report requested)

  • The report is ready for viewing (Click to view report)

Dynatrace Network Analyzer request time (id: avRequestTime)

The time when a Transaction Trace report was requested from the CAS.

Failed transaction event (id: stopEvent)

internalId: stopEvent

descriptionTmxId: RTM_DV_TRANS_HELP_DIMENSION_stopEvent

!!! FIXME Description missing in TMX !!!

Hour of the day (id: hrD)

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

Is front-end tier? (id: isFrontEndTier)

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

Last heartbeat (id: heartbeat)

The time stamp of the last detected activity.

Link to Dynatrace Network Analyzer file (id: avTraceLink)

A link to the Transaction Trace file.

Link to Dynatrace Network Analyzer report (id: avReportLink)

A link to the Transaction Trace report.

Location ID (id: locID)

Location ID

Primal AMD UUID (id: AmdUUID)

Primal AMD UUID

Process ID (id: processId)

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

Reporting group ID (id: bgID)

Reporting group ID

Sample timestamp (id: origSampTs)

internalId: origSampTs

descriptionTmxId: RTM_DV_TRANS_HELP_DIMENSION_origSampTs

!!! FIXME Description missing in TMX !!!

Screenshot (id: ssLink)

Transaction Trace screenshot.

Screenshot thumbnail (id: ssLinkThumbnail)

Transaction Trace screenshot thumbnail.

Tier (id: bgnameTier)

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.

Time (id: begT)

The time stamp of the data presented on the report.

Transaction (id: bgTrans)

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

Transaction GUID (id: transGUID)

The identification number of a transaction.

Transaction source (id: transSource)

Informs whether the transaction comes from Synthetic Monitoring probes, Agentless Monitoring Device, or is user-defined.

Transaction timestamp (id: transTimestamp)

The exact time when the transaction occurred.

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.

Synthetic and sequence transaction data metrics

Aborted transactions

The number of aborted transactions (transaction error code: -3). An aborted transaction is reported when one or more consecutive URLs detected in the traffic match the defined transaction steps, but the next URL detected does not match the transaction definition.

Aborted transactions per minute

The number of aborted transactions, per minute.

Affected users (availability)

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

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.

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 Monitoring Visibility

Application Monitoring visibility.

Application performance

For transactional protocols, this is the percentage of software service transactions 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.

Application processing time

Sum of transfer time for operations in which the server for the given transaction played the actual role of the server plus sum of time between operations but only if the second operation client played the role of the server for given transaction. See the basic transaction model for reference.

graphical illustration

Attempts

Attempts

Attempts (transport)

The total number of transactions, including transactions with errors.

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).

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 packets

The number of packets sent by the client.

Client packets/sec

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

Client response time

Client response time is calculated for operations in which the client for a given transaction played the role of the server. It is a sum of transfer time for such operations.See the basic transaction model for reference.

graphical illustration

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 time

Client time is the time interval between the last data packet from transaction response message from TCP session server to the first packet of the acknowledgment from TCP session server to the client. Client time is similar to server time, but measured in context of transaction response message.

Client time (failed transactions)

The client time for all failed transactions (transactions with a -2 status code). This metric is valid only for 'Transactions (Synthetic Monitoring)' transaction source.

Client time (requests)

The client time for all transaction requests (both requests that became successful transactions and requests that ended as transactions with errors). This metric is valid only for 'Transactions (Synthetic Monitoring)' transaction source.

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.

End-to-end RTT

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

Errors

The total number of TCP and SSL errors.

Failed transactions

For Synthetic Monitoring transactions, it is the number of transactions for which the give-up threshold was exceeded. For RUM transactions, failed transactions are all transactions with status other than -3 (aborted).

Failed transactions per minute

The number of failed transactions, per minute.

Failed transactions time breakdown (Active Monitoring)

The breakdown of trace time into client time, network time, server time, calculated only for unavailable transactions.

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 transactions

The number of transactions for which the transaction time was below a predefined threshold value.

Fast transactions 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.

HTTP abort error

This error is reported when one of the URLs in a transaction detected in a monitored traffic does not match the transaction definition. This refers to any URL in a sequence of URLs, except the firs one.

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.

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 of 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 3rd category contains no default error types assigned, and can be configured by a user. Finally, a group of Other HTTP (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 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 server errors (5xx)

The number 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 timeout error

This type of error is reported if the time between the occurrence of consecutive URLs constituting a transaction exceeds the predefined timeout value.

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.

Incomplete transaction error

This error tells us that transaction was reported although monitored traffic did not match the first steps in the transaction definition.

Max giveup time threshold

The maximum time after which a Synthetic Monitoring transaction is considered incomplete.

Max slow transaction threshold

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

Min giveup time threshold

The minimum time after which a Synthetic Monitoring transaction is considered incomplete.

Min slow transaction threshold

The minimum slow transaction threshold.

Network time

The time the network takes to deliver the request to the server and to deliver the resulting response back to the user. In other words, network time is the portion of the operation time that is spent on transferring data over the network.

Network time (failed transactions)

The network time for all failed transactions (transactions with a -2 status code). This metric is valid only for 'Transactions (Synthetic Monitoring)' transaction source.

Network time (requests)

The network time for all transaction requests (both requests that became successful transactions and requests that ended as transactions with errors). This metric is valid only for 'Transactions (Synthetic Monitoring)' transaction source.

No response error

The number of errors of the category No response. These errors are reported when a request is detected in the monitored traffic, but the actual operation following this request is not observed.

Number of results

Depending on the transaction source, the number of results may mean:

  • For RUM transaction: the number of subcomponents of error-free transaction. Note that this metric is recorded at the time when the monitored transaction is closed.

  • For Private Enterprise transaction: the number of transaction requests.

  • For RTMS transaction: the number of records returned by a particular RTMS timer.

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.

Percentage of affected users (availability)

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

Percentage of affected users (performance)

The percentage of users that experienced application performance problems.

Percentage of slow transactions

The percentage of transactions for which the transaction time was above a predefined threshold value.

Requests

The number of all transactions request, both successful transactions and transactions with errors.

RTT measurements

The number of RTT measurements.

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 packets

The number of packets sent by the servers.

Server packets/sec

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

Server RTT

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

graphical illustration

Server time

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

Server time (failed transactions)

The server time for all failed transactions (transactions with a -2 status code). This metric is valid only for 'Transactions (Synthetic Monitoring)' transaction source.

Server time (requests)

The server time for all transaction requests (both requests that became successful transactions and requests that ended as transactions with errors). This metric is valid only for 'Transactions (Synthetic Monitoring)' transaction source.

Slow transactions

The number of transactions for which the transaction time was above a predefined threshold value.

Slow transactions 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.

Time resolution

Time resolution.

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 packets

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

Total packets/sec

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

Trace time breakdown

The breakdown of trace time into client, network and server time.

Trace time breakdown (unavailable)

For Synthetic Monitoring unavailable transactions, this is the breakdown of transaction time into client time, network time and server time.

Trace time percentage breakdown

The percentage breakdown of trace time into client, network and server time.

Trace time percentage breakdown (unavailable)

For Synthetic Monitoring unavailable transactions, this is the percentage breakdown of transaction time into client time, network time and server time.

Transaction percentage breakdown

Transaction percentage breakdown into slow and fast transactions.

Transaction request percentage breakdown

The percentage breakdown of all transaction requests into requests that ended as fast, slow and unavailable transactions in case of Synthetic Monitoring transactions, and into fast, slow, aborted and failed in case of Data Center RUM transactions.

Transaction requests

The number of all transaction requests, both requests that became successful transactions and requests that ended as transactions with errors.

Transaction requests breakdown

In case of Synthetic Monitoring transactions, the breakdown of all transaction requests into requests that became slow, fast and unavailable transactions. In case of RUM transactions, the breakdown of all transaction requests into requests that ended as slow, fast, aborted and failed transactions. As transaction requests we understand both requests that became successful transactions and transactions with errors. For RTMS transactions, use the "Transactions breakdown" metric.

Transaction requests time breakdown

The breakdown of trace time into client time, network time, server time, calculated for transactions coming from Synthetic Monitoring agents.

Transactions

The number of transactions.

Transactions/min

The number of transactions per minute.

Transactions/sec

The number of transactions per second.

Transactions breakdown

Transaction breakdown into numbers of slow and fast transactions.

Transactions per minute

The number of operations per minute.

Transaction time

The time it took to complete a transaction.

Transaction time breakdown

The transaction time breakdown into client time, client response time, server time, network time and application processing time.

Transaction time percentage breakdown

The breakdown of the average value of operation time into percentage client time, client response time, server time, network time and application processing time.

Unavailability (total)

Unavailability calculated as Availability (total) - Failures (total).

Unavailable transactions

The number of unavailable transactions (transaction error code: -2). An unavailable transaction is reported when the time between the occurrence of consecutive URLs constituting a transaction, or the whole transaction exceeds the predefined timeout value.

Unavailable transactions per minute

The number of unavailable transactions, per minute.

Unique users

The number of unique users detected in the monitored traffic.

 

  • No labels