Response Time - Attributes listed alphabetically

This section includes an alphabetical listing of all attributes that are included in the various Response Time attribute groups, along with a description for each attribute. Note that there are some cases where the same attribute name is defined more than once. This signifies that it is being used slightly differently in different attribute groups.

Abort On Violation

Specifies whether the robotic script is stopped when an availability violation occurs (True or False).

Active Connections

The total number of active TCP socket connections created during the current aggregate interval.

Additional Details

Any additional details about the event.

Agent

The name of the monitoring agent.

Agent Type

The type of data collector (Web Response Time, Robotic Response Time, or Transaction Reporter) that collected the particular data record. The monitoring software returns one of the following values:
  • Robotic Response Time
  • Web Response Time
  • Transaction Reporter (for Transaction Tracking)

Aggregate Applications Uniquely

Specifies how the agent collects aggregate data that matches the defined application pattern (True or False). This attribute is used with the Application Pattern, Transaction Pattern, and Aggregate Transactions Uniquely attributes to determine the granularity of data collected. Valid values for this attribute are:
  • True

    The agent aggregates data uniquely and generates a unique record for each transaction whose application name matches the value of the Application Pattern attribute. It also provides a statistical summary for each transaction that matches the specified application pattern during the specified hour. This attribute value produces multiple records and increases the amount of overhead in terms of the amount of data that the monitoring agent collects, retains in the database, and displays.

  • False

    The agent aggregates by pattern and creates a single aggregate record, named with the value in the Application Name attribute, that represents the summarized information from all transactions that matched the defined application pattern.

Aggregate Transactions Uniquely

Specifies how the agent collects aggregate data that matches the defined transaction pattern (True or False). Valid values are:
  • True

    The agent aggregates data uniquely and generates a unique record for each transaction that matches the value in the Transaction Pattern attribute.

  • False

    The agent aggregates by pattern and creates a single aggregate record, named using the value of the Transaction Name attribute, that represents the summarized information from all transactions that matched the defined transaction pattern.

Aggregate By

Specifies how the Web Response Time monitoring agent aggregates its collected low level TCP data, by client, server, component, protocol, or a combination of these groups.

Aggregated Uniquely By

Specifies how the monitoring agent aggregates its collected data, aggregating by application, client, transaction, or a combination of these groups.

Aggregated Uniquely By (ISM)

Specifies how the Internet Services Monitoring data is to be aggregated (None, Profile, Profile_Host, Profile_Service, or Profile_Agent). For example, if aggregation is by Profile, then the profile is the only key filled in; if aggregation is by Profile_Host, then only the profile host name is filled in.

Aggregates Uniquely

Specifies how the agent collects aggregate data that matches the defined client pattern (Aggregates Uniquely or Aggregate by Pattern). Valid values are:
  • Aggregate Uniquely

    The agent aggregates data uniquely and generates a unique record for each client that matches values in either the Client IP Pattern or Client Hostname Pattern attribute.

  • Aggregate by Pattern

    The agent creates a single aggregate record (the name is in the Client Name attribute) that represents the summarized information from all client transactions that matched the defined client pattern.

Alert Name

The name of the SSL Alert (such as Decryption Failed or Certificate Expired).

Alert Type

The type of SSL alert (valid values are Network Error, Server Error, Server Warning, Client Error, or Client Warning).

App Server

The application status at the application server tier (Good, Fair, or Poor).

Application (Application Name)

The name of the monitored application reported to the Application Management Console. In Robotic Response Time, the application name is provided by ARM instrumentation. In Web Response Time, the name is part of the URL. If you define the Application Pattern attribute, and set the value of the Aggregates Uniquely attribute to false, the value of this attribute is the name of the Application Pattern.

Application Key

The alias name of the subnode for the current application.

Application Name

The name of the monitored application reported to the Application Management Console. In Robotic Response Time, the application name is provided by ARM instrumentation. In Web Response Time, the name is part of the URL. If you define the Application Pattern attribute, and set the value of the Aggregates Uniquely attribute to false, the value of this attribute is the name of the Application Pattern.

Application Pattern

The pattern syntax for the name of the application to monitor.

Application Protocol

The protocol used by the monitored application, such as HTTP or HTTPS.

Attributes

A list of user-defined attributes for the robotic script.

Auth Type

The type of authorization for the user name specified in the User Name attribute. You can enter an alphanumeric string with a maximum of 32 characters.

Average Client Time

The average elapsed time, in seconds, from the start of a transaction to the start of outbound network activity for the client. It also includes the average elapsed time from the last network update of the transaction to the end of the transaction. For instance data, this field is an absolute value, not an average.

For the Robotic Response Time agent, average client time indicates the average time that a robotic script takes to run in the runtime environment. The average client time that Robotic Response Time agent scripts returns includes factors such as script initialization overhead, and verification point processing. In some cases, the average client time can be zero, because the Robotic Response Time agent does not report values less than one millisecond.

If the Robotic Response Time agent reports unusually high average client time for script playbacks, this can indicate that there are too many scripts competing for memory or CPU. In some cases, high average client time is associated with a script timeout exception. In other cases, increases in average client time can be attributed to increases in server time and/or network time.

Average Connect Time

The average elapsed time, in seconds, from the time a user requests a browser connection to when the browser connects successfully with the server. If the transaction is interrupted or canceled before the connection is achieved, the elapsed time between the request and the interruption is reported. For instance data, this field is an absolute value, not an average.

Average DNS Time

The average elapsed time, in seconds, to look up the Domain Name System (DNS) address of the website. For instance data, this field is an absolute value, not an average.

Average Download Time

The average elapsed time, in seconds, from the time that the connection is made with a web server to successfully downloading a web page. For non-browser applications, this attribute reports the overall response time. For instance data, this field is an absolute value, not an average.

Average Failed Users

The average number of unique users experiencing Failed performance (a failed transaction). For example, if the user at IP address 128.1.2.3 experiences a Failed performance for a single WRT transaction, and the same user later experiences Failed performance during the same time period, that user is counted only once in both the Failed count and the All count. For the attribute groups that monitor a specific time interval, the value is the actual count for the time period (see Total Failed Users). For all of the Current Status and Summary attribute groups, the values are averages.

Average Good Users

The average number of unique users experiencing Good performance (not a failed transaction and not slower than the minimum response time threshold). For example, if the user at IP address 128.1.2.3 experiences a Good performance for a single Web Response Time transaction, and the same user experiences Good performance again during the same time period, that user is counted only once in both the Good count and the All count. For the attribute groups that monitor a specific time interval, the value is the actual count for the time period (see Total Good Users). For the Current Status and Summary attribute groups, the values are averages.

Average Load Time

The average elapsed time, in seconds, from the time the user requests a download to the completion of the web object download..

Average Network Time

The average elapsed time, in seconds, spent transmitting all required data through the network. This is a calculated time. For instance data, this field is an absolute value, not an average.

Average Object Count

The average number of objects embedded in a web page for the time period.

Average Object Size

The average size of all objects embedded in the web page for the time period.

Average Page Views Per Session

The average number of page views per user session.

Average Render Time

The total time taken, in seconds, to download, parse, and render the page from the user perspective.

Average Requests

The average number of requests for a data interval during the time span for which data is displayed.

Average Resolve Time

The average amount of time, in seconds, required to resolve the domain name of the URL. The resolve time is a part of the overall network time. For instance data, this field is an absolute value, not an average.

Average Response Time

The average response time, in seconds, for a single transaction instance that was observed during the monitoring interval. During each monitoring interval, minimum, maximum, and average response times for the aggregate records are recorded. Use these attributes to analyze the range of response times for the transaction.

Average Server Response Time

The average elapsed time, in milliseconds, for an overall server transaction to complete. For instance data, this field is an absolute value, not an average.

Average Server Time

The average elapsed time, in seconds, that a transaction spends running on the server during the current monitoring interval. For a transaction instance, this value is an absolute time, not an average.

Average Session Duration

The average duration, in seconds, of user sessions for the time period.

Average Slow Users

The average number of unique users experiencing slow performance (not a failed transaction, but slower than the minimum response time threshold) during the time period. For example, if the user at IP address 128.1.2.3 experiences a slow performance for a single WRT transaction, and the same user later experiences slow performance again during the same time period, that user is counted only once in both the Slow count and the All count. For the attribute groups that monitor a specific time interval, the value is the actual count for the time period (see Total Slow Users). For the Current Status and Summary attribute groups, the values are averages.

Average Users

The average number of unique users for the time period, or if no user or session tracking is configured, the number of unique source IP addresses. A user that experiences a Good, Failed, or Slow performance for a single Web Response Time transaction is counted once. For attribute groups that monitor a specific time interval, the value is the actual count for the time period (See Total Users). For the Current Status and Summary attribute groups, the values are averages.

Back Status

The application status at the backend tier (Good, Fair, or Poor).

Bad Requests

The number of transactions that did not complete correctly or reported an error during the data interval.

Browser Description

A description of the web browser on which the web page is displayed.

Captured Content Location

The location of the captured content.

Checksum

The checksum of the robotic script file.

Client

The name of the client that initiated the request (or transaction).

Client Errors

The number of HTTP requests with a status code between 400 and 499.

Client Group

The client group of the monitored traffic displayed as an IP address, or as an IP mask for multiple client addresses.

Client Hostname Pattern

The pattern, representing a set of fully qualified hostnames, that defines the hostnames of the clients to monitor. Example: a pattern to match all hostnames ending with ibm.com: *.ibm.com.

Client IP Pattern

The pattern, representing a set of client IP addresses, that defines the IP addresses of the clients to monitor. Example: a subnet such as 9.48.24.*. Only transactions from client IP addresses that match this user-defined pattern are recorded.

Client Key

The alias name of the subnode for the current client.

Client Name

A user-defined name for the monitored client that initiated the request. When defining a client pattern, if you select to aggregate by pattern, then the unique IP address and hostname that matches the defined pattern are replaced by the Client Name and aggregated together with all other unique clients that also matched the defined pattern.

Client Status

The application status at the client tier (Good, Fair, or Poor).

Client Time

The average elapsed time, in seconds, that the transaction spends running on the client during the current monitoring interval. For a transaction instance, this value is an absolute time, not an average.

For the Robotic Response Time agent, client time indicates the time that a robotic script takes to run in the runtime environment. The client time that Robotic Response Time agent scripts returns includes factors such as script initialization overhead, and verification point processing. In some cases, the client time can be zero, because the Robotic Response Time agent does not report values less than one millisecond.

If the Robotic Response Time agent reports unusually high client time for script playbacks, this can indicate that there are too many scripts competing for memory or CPU. In some cases, unusually high client time is associated with a script timeout exception. In other cases, increases in client time can be attributed to increases in server time and/or network time.

Draft comment:
KOR: enhancing description as per PMR 22601,7TD,000

CLI Playback Command

The command and associated options that run a robotic script. If the script has not been uploaded to the depot, you must provide the full path name to the command. You can enter an alphanumeric string with a maximum of 128 characters.

CLI Success RC

The return code that a CLI script returns when it runs successfully.

Collect Instances

Specifies whether to collect every instance (True, False, or On Failure). These values are further defined as follows:
  • True

    Collects all instance data. This includes performance data for every transaction that matches the specified IP address, URL, or data pattern. For a high-traffic website, a large amount of performance data can quickly accumulate.

  • False

    Collects no instance data. It disables the collection of instance data and only collects a single statistical summary record for the aggregate interval. This choice provides a single record and the lowest overheard in terms of the amount of data that the monitoring agent collects, retains in the database, and displays.

  • On Failure

    Collects transaction instance data after a violation occurs.

Component

The monitoring agent ( RPT, or WRM) that generated the message. RPT indicates Robotic Response Time, and WRM indicates Web Response Time.

Component

The component name of the monitored traffic as specified in the Component definition in the Application Management Configuration Editor.

Concurrent

Specifies if several instances of the same command can be run concurrently (True or False). If concurrent playback causes performance or other problems, set this option to False, otherwise all non-concurrent commands are queued and run sequentially. All concurrent commands are run simultaneously and are not affected by non-concurrent commands.

Config Name

The name of the client group or transaction.

Config Type

The type of configuration (can be Transaction or Client; for Web Response Time agents, this can also be Network Flow or Transaction Group).

Content Error Search String

A text string containing information about the error condition associated with content checking.

Content Error Type

The type of content checking error. Valid values include:
  • 0 = None
  • 1 = Page Title Found
  • 2 = Page Title Not Found
  • 3 = Content Found
  • 4 = Content Not Found

Count

The number of times that the specified SSL Alert occurred on the specified server during the current summary interval.

Current Requests

The total number of requests during the current data interval, displayed for the highest priority monitoring agent (if multiple agents are monitoring the same application). The order of precedence is 1) Transaction Reporter, 2) Web Response Time, and 3) Robotic Response Time. For example, if two robotic agents and a Web Response Time monitoring agent all monitor the same application, the status for the Web Response Time monitoring agent takes precedence.

Current Run Status

Table 1. The status of the current robotic script playback.
Value Description of the value
None There is no playback recorded.
Idle No playbacks are currently in progress.
In_Progress The playback is running.
Complete The monitor ran successfully.
Timeout The current playback timed out.
Overrun The current run did not finish before the next run was scheduled.
Queued The current playback is waiting.
Failed The playback failed.
Error There was an error reported.
Not Supported The script type is not supported.

Current UUID

A unique identifier used with the Root UUID and Parent UUID attributes to completely identify a specific subtransaction in your environment.

Data

The text block of configuration data that is being transferred for a profile, transaction, or client group between the Application Management Configuration Editor and a configuration file stored in the Application Management Console monitoring agent.

Data Collector Type

The type of data collector (Web Response Time, Robotic Response Time, or Transaction Reporter) that collected the particular record.

Data Interval

The frequency, in seconds, that indicates how often the monitoring agent collects data.

Data_Len_Post

The actual length, in bytes, of the text block of configuration data that is transferred. It might take several transfers to read or write the configuration file for a profile, transaction, or client group.

Data_Len_Pre

The length of the text block of configuration data stored in the Data attribute before a transfer. It might take several transfers to read or write the configuration file for a profile, transaction, or client group.

Data Time Span

The amount of time, in hours, during which data is collected (default: 8 hours). You can configure this value for the monitoring agent.

Data Timezone Offset

The time zone offset (from Greenwich Mean Time), in seconds, for the displayed data.

Date Modified

The date and time when the robotic script file was last modified.

Depot Node

The name of the subnode.

Description

The user-defined description of the robotic script file.

Description (ISM)

The description of the Internet Services Monitoring element.

Destination Hostname

The destination hostname of the transaction.

Destination IP

The destination IP address of the transaction.

Destination Node

The destination node of the transaction (for internal use only).

Destination Port

The destination IP port of the transaction.

End Time

The aggregation end time when the monitoring agent stopped collecting data. It uses the MM/DD/YY HH:MM:SS format, using GMT (Greenwich Mean Time). Example 01/03/08 12:05:03 indicates the aggregate value for the time period was 12:05 to 12:10 p.m on January 3, 2008.

End Time

The end time of the most recent interval for TCP data across all monitored components. This time is for internal use only and should not be used in situations.

Entry Type

The type of configuration entry (Include, Exclude, Reporting, or Property).

package test;
import org.eclipse.hyades.test.common.event.EventProperty;
import org.eclipse.hyades.test.common.event.VerdictEvent;
import com.ibm.rational.test.lt.kernel.services.ITestExecutionServices;
import com.ibm.rational.test.lt.kernel.services.ITestLogManager;
/**
* @author unknown
*/
public class MyCustomCode implements
com.ibm.rational.test.lt.kernel.custom.ICustomCode2 {
/**
* Instances of this will be created using the no-arg constructor.
*/
public MyCustomCode() {
}
/**
* For javadoc of ICustomCode2 and ITestExecutionServices interfaces, select 'Help
* Contents' in the Help menu and select 'IBM Rational Performance Tester TES'.
*/
public String exec(ITestExecutionServices tes, String[] args) {
//Create the event
ITestLogManager tlm = tes.getTestLogManager();
VerdictEvent verdict = new VerdictEvent();
verdict.setCausedBy("CausedBy Description: custom code VP failure.");
verdict.setEventType("MyCustomEvent");
verdict.setText("Text message: force VP failure in Custom RPT code");
verdict.setReason(VerdictEvent.REASON_SEE_DESCRIPTION);
verdict.setVerdict(VerdictEvent.VERDICT_FAIL);
//Optionally set expected and actual runtime values
EventProperty expected = new EventProperty();
expected.setName("Expected");
expected.setValue("Sample expected value");
expected.setType("String");
verdict.addProperty(expected);
EventProperty actual = new EventProperty();
actual.setName("Actual");
actual.setValue("Sample actual value");
actual.setType("String");
verdict.addProperty(actual);
//Send the event
tlm.reportEvent(verdict);
return null;
}

Event Timestamp

A timestamp indicating data collection times and the time that events occur. To specify a time and date for comparison and testing, use attributes from the IBM Tivoli Monitoring Universal Time or Local Time attribute groups.

Event Type

The type of event. The following table describes the events;
Table 2. Event Types

Event Type Value Source Description

Authentication Failure

 

An HTTP authorization failure (HTTP code 401 or 407) occurred during playback.

Component Failure

 

A failure occurred to the Internet Service Monitoring, Response Time, or Transaction Tracking components.

Content Failure

Rational Performance Tester

The content returned is unexpected. A content verification point verifies that the returned response contains or does not contain an expected string.

Content Size

Rational Performance Tester

The byte count returned does not match the byte count specified in a verification point. A response size verification point verifies that the number of bytes returned in a response matches an exact value or is within a range.

Custom Failure

Rational Performance Tester

A failure occurred based on a custom verification point added to the test log with custom code.

Expected Data Failure

Rational Functional Tester

The expected data value and actual data value do not match during playback.

Expected Image Failure

Rational Functional Tester

The expected image and actual image that was found during playback do not match.

Expected Property Failure

Rational Functional Tester

The expected property value and actual value was found during playback do not match

Expected Text Failure

 

The expected text and actual text that was found during playback do not match

Generic Failure

 

An error occurred on playback, but no error code is returned.

HTTP Return Code

Rational Performance Tester

The returned response code does not match the expected value. A return code verification point verifies that the returned response code matches an expected value. For the expected value, you can indicate an exact response code or specify that the response code is within a specified list or category.

Page Title Failure

Rational Performance Tester

The returned page title is unexpected. Page title verification points verify that the primary request for a page returns the expected page title. The page title comparison is case-sensitive, but ignores multiple white-space characters, such as spaces, tabs, and carriage returns.

Return Code

 

An unexpected return code was returned during playback or a time-outs has occurred.

Timeout

 

The page is not responding in the expected time frame. This event type is returned if you set the playback parameters too small. You can increase the parameter in the Application Management Console Timeout section of the script properties.

URL Unavailable Failure

Rational Performance Tester

The requested page is unavailable. This is a verdict error. You see a page verdict only if a connection problem occurs or if you set verification points.

Verification Point Failure

 

A breach of parameter values set in a verification point occurred during playback. This is a catch all event type used when none of the others match.

Expected Data

The return code returned by the CLI command. The default expected return code for most executable commands and scripts is 0. Script writers can cause their scripts to exit with unexpected return code values to indicate to the software that an error occurred. If the command returns a value that does not match the expected return code value, then the monitor fails the transaction and optionally sends an Expected Return Code failure event if one is defined for the monitor.

Failed

The number of failed Internet Services Monitoring attempts.

Failed Requests

The number of recorded transactions that either did not complete correctly, or reported an error during the monitoring interval, or whose response time was greater than or equal to the Maximum Response Time Threshold. Failed status is indicated by a transaction Status Code with a value greater than 0. This value is added to the values of the Slow Requests and Good Requests attributes to obtain the value of the Total Requests attribute.

Fail Code

The underlying file system-specific failure code for a failed transfer. Examples include a POSIX errno value or a WIN32 GetLastError() code.

Fail Type

The type of fail (POSIX or WIN32) reported by the Fail Code attribute.

File Mod1 Post

The low-order word portion of the last time that a configuration file was modified after a transfer. This is useful to ensure that the file has not changed between transfers if multiple transfers are needed to read or write the file. The high-order word portion is stored in the File Mod2 Post attribute.

File Mod1 Pre

The low-order word portion of the last time that a configuration file was modified before a transfer. This is useful to ensure that the file has not changed between transfers if multiple transfers are needed to read or write the file. The high-order word portion is stored in the File Mod2 Pre attribute.

File Mod2 Post

The high-order word portion of the last time that a configuration file was modified after a transfer. This is useful to ensure that the file has not changed between transfers if multiple transfers are needed to read or write the file. The low-order word portion is stored in the File Mod1 Post attribute.

File Mod2 Pre

The high-order word portion of the last time that a configuration file was modified before a transfer. This is useful to ensure that the file has not changed between transfers if multiple transfers are needed to read or write the file. The low-order word portion is stored in the File Mod1 Pre attribute.

File Size

The size, in bytes, of the robotic script file.

File Type

The type of robotic script (CLI Playback, Rational Performance Tester, or Mercury LoadRunner).

First Occurrence

The timestamp of the first occurrence of the SSL Alert in the current interval.

Generic Playback Command

The command and options that run a robotic script. If the script has not been uploaded to the depot, you must provide the full path name to the command. You can enter an alphanumeric string with a maximum of 128 characters.

GMT Offset

The difference in the number of hours between Greenwich Mean Time and the time used by the web server.

Good

The number of good Internet Services Monitoring attempts.

Good Requests

The number of recorded transactions that completed successfully, and whose response time was less than the Minimum Response Time Threshold. This value is added to the values of the Slow Requests and Failed Requests attributes to obtain the value of the Total Requests attribute.

Good Requests

The number of recorded transactions that completed successfully.

Hidden

Indicates if the robotic script is a hidden file.

Host

The Internet Services Monitoring host name (example: www.ibm.com).

Host

The TCP/IP host name of the computer on which the client or server is running.

Hostname

The TCP/IP host name of the computer on which the client or server is running.

IdentChecksum

Identifies an Internet Services Monitoring data point for launching in context.

Importance

The business value of the transaction (values, listed in increasing order of importance, include Discretionary, Very Low, Low, Medium, High, Very High, or Highest). You define this indicator in the transaction profile using the Application Management Configuration Editor. Note that the value of this attribute can affect the sorting of ranked applications in certain workspace views. For example, applications that are ranked and displayed in the Applications Availability Historical Summary view of the Applications workspace are displayed sorted by rank values, but these rank values are calculated based on percent failed and slow, but also on Importance values.

Informational

The number of HTTP requests with a status code between 100 and 199.

Instance Root

The unique identifier that pinpoints a particular transaction instance. Use this value with the Root UUID, Parent UUID, and Current UUID attributes to completely identify a specific subtransaction instance in your environment.

IP

The IP address of the server that processed the transaction. Restricting monitoring to one or more IP addresses is useful when you want to monitor transaction performance for a subset of users, such as a specific IT group in one of your internal corporate divisions. The format of this attribute is an alphanumeric string up to 16 characters, specifying either the IP address or a pattern.

IP Destination Address

The IP address (or pattern) for one or more server computers that process page requests. Enter an alphanumeric string up to 16 characters to specify the IP address or enter a pattern.

IP Destination Port

The port number of the server that processes page requests.

IP Source Address

The IP address of the client that originates the page request. Restricting monitoring to one or more IP addresses is useful when you want to monitor transaction performance for a subset of users, such as a specific IT group in one of your internal corporate divisions. Enter an alphanumeric string up to 64 characters to specify the IP address or enter a pattern.

IPV6

The IP (version 6) address of the server that processed the transaction. Restricting monitoring to one or more IP addresses is useful when you want to monitor transaction performance for a subset of users, such as a specific IT group in one of your internal corporate divisions. The format of this attribute is an alphanumeric string up to 16 characters, specifying either the IP address or a pattern. See the IBM Tivoli Monitoring Support Portal (http://www-306.ibm.com/software/sysmgmt/products/support/IBMTivoliMonitoringV6.html) for more information on the IPV6 environment.

Key Name

The name of the configuration entry key.

KiloBytes Retransmitted

The number of kilobytes that were retransmitted.

Last Run Duration

The time, in seconds, that the most recent robotic script playback has been running.

Last Run Start Time

The start date and time of the most recent robotic script playback. The valid format is a 12 character timestamp. To specify a time and date for comparison and testing, use attributes from the IBM Tivoli Monitoring Universal Time or Local Time attribute groups.

Last Run Status

The status of the most recent robotic script playback.

Last Update

The time of the last depot update.

Last Updated

The last date and time when the robotic playback status was updated.

Last Updated

The last date and time when the Application Management Console agent collected data for a workspace.

Latency Time

The time it takes for a client to receive a 0-byte TCP response packet after sending a 0-byte TCP request packet.

Marginal

The number of marginal Internet Services Monitoring attempts.

Max Requests

The maximum number of requests for a data interval during the time span for which data is displayed.

Maximum Response Time

The maximum response time, in seconds, for a single transaction instance that was observed during the monitoring interval. During each monitoring interval, minimum, maximum, and average response times for the aggregate records are recorded. Use these attributes to analyze the range of response times for the transaction.

Maximum Response Time Threshold

The maximum acceptable response time, in seconds, for a transaction to complete before it is marked as Failed. This attribute is an optional value that you can use when defining a new transaction pattern, and is initially displayed as a blank table cell, indicating that no maximum threshold is defined. Setting this value determines how the monitoring agent classifies and reports transaction response time data. All transactions with a response time greater than this value are marked as Failed in reports. For example, if this value is set to 10, then all transactions with a response time greater than or equal to 10 seconds are Failed transactions. This value is displayed as a decimal formatted to 3 decimal places.

Message Date and Time

The date and time that the message was generated. The message includes a timestamp in the format MM/DD/YY HH:MM:SS. For example, 01/23/07 18:32:03 indicates the message was generated on January 23, 2007 at 18:32:03.

Message ID

The unique ID assigned to the message when it is generated. The message ID must conform to the Tivoli Message Standard.

Message Source

Additional information about the component from which the message was generated.

Message Text

The message text that is generated by the monitoring software.

Method

The method used for performing HTTP requests (GET, POST, HEAD, PUT, OPTIONS, DELETE, TRACE, or CONNECT).

Min Requests

The minimum number of requests for a data interval during the time span for which data is displayed.

Minimum Response Time

The minimum response time, in seconds, for a single transaction instance that was observed during the monitoring interval. During each monitoring interval, minimum, maximum, and average response times for the aggregate records are recorded. Use these attributes to analyze the range of response times for the transaction.

Minimum Response Time Threshold

The maximum acceptable response time, in seconds, for a transaction to complete before it is marked as Slow. If the response time is also greater than the Maximum Response Time Threshold, it is marked as Failed. This attribute is an optional value that you can use when defining a new transaction pattern. Setting this value determines how the monitoring agent classifies and reports transaction response time data. All transactions with a response time greater than this value are marked as Slow in reports. For example, if this value is set to 8, then all transactions with a response time greater than 8 seconds (and less than the Maximum Response Time Threshold) are Slow transactions. This value is displayed as a decimal formatted to 3 decimal places.

Module Name

The name of the decoder module from which the data is derived.

Msg Status

The application status at the messaging tier (Good, Fair, or Poor).

Name

The user-defined name for the robotic script.

Network Time

The average time, in seconds, spent transmitting through the network all of the required data for the transaction.

Network Time

The average time, in seconds, spent transmitting through the network all of the required data for the transaction.

New Connections

The total number of new TCP socket connections created during the current aggregate interval.

Number Active Sessions

The number of active user sessions.

Number Browser Connections

The number of transactions that are associated with connecting to a web browser.

Number of Content Check Errors

The number of requests with content check errors.

Number of fatal client SSL alerts

The total number of fatal SSL Alerts of type Client Error encountered by the server during the current monitoring interval. The SSL connection failed because the client did not send a valid certificate requested by the server, or the client does not support the minimum set of SSL features expected by the server.

Number of fatal server SSL alerts

The total number of fatal SSL Alerts of type Server Error encountered by the server during the current monitoring interval. The SSL connection failed because the server did not send a valid certificate requested by the client.

Number of fatal SSL alerts

The total number of fatal SSL Alerts encountered by the server during the current monitoring interval.

Number of network SSL alerts

The total number of SSL Alerts of type Network Error encountered by the server during the current monitoring interval. The SSL connection failed because the packet data was corrupted during network transmission.

Number of warning client SSL alerts

The total number of warning SSL Alerts of type Client Error encountered by the server during the current monitoring interval. The SSL connection resulted in a warning because the client did not send a valid certificate requested by the server.

Number of warning server SSL alerts

The total number of warning SSL Alerts of type Server Error encountered by the server during the current monitoring interval. The SSL connection resulted in a warning because the server did not send a valid certificate requested by the client.

Number of warning SSL alerts

The total number of warning SSL Alerts encountered by the server during the current monitoring interval.

Number Failed Sessions

The number of failed user sessions.

Number Good Sessions

The number of good user sessions.

Number of 403s

The number of HTTP requests with the status code 403.

Number of 404s

The number of HTTP requests with the status code 404.

Number of 500s

The number of HTTP requests with the status code 500.

Number Retries

The number of times to retry the transaction after the first attempt fails. For example, if the value of this attribute is 4, the transaction will be attempted up to 5 times (the initial attempt plus four specified retries) before generating an event.

Number of Sessions

The number of user sessions.

Number of Requests

The number of requests.

Number of Retransmissions

The number of packets retransmitted.

Number Slow Sessions

The number of slow user sessions.

Offset Post

The file offset read or write position after a transfer, when multiple transfers are needed to read or write a configuration file.

Offset Pre

The file offset read or write position before a transfer, when multiple transfers are needed to read or write a configuration file.

Origin Node

The name of the host subnode.

Overall Status

The overall status (Good, Warning, or Critical) of the application, based on metric data collected during the monitoring interval, such as the number of failing transactions and the number of slow transactions. Individual monitoring agents collect violation data. The Application Management Console polls the individual monitoring agents and summarizes the collected data to arrive at the overall status for the monitoring interval.

The value of the Application Management Console Overall Status attribute is determined by failing (critical) transactions, and slow (warning) transactions.

As the Application Management Console collects data from the agents, it merges all the status data from all of the agents in the Transaction tables, and then again for the Application tables. The highest severity status during the monitoring interval is displayed. Consider the following example of data collected for a Web Response Time agent:

Table 3. Example Application Management Console status
Application Transaction Agent Number of failures Number of slow
App1 Trans1 Agent1 0 2
App1 Trans1 Agent2 2 0
App1 Trans2 Agent1 0 0
App1 Trans3 Agent1 0 1

The Transaction workspaces for the Application Management Console agent show the overall status for each transaction. In this table, the two rows for Trans1 are combined into one row with an overall status of Critical (worst status for the transaction).

Table 4. Overall Status for sample Application Management Console transactions
Application Transaction Overall Status
App1 Trans1 Critical
App1 Trans2 Good
App1 Trans3 Warning

The Application Management Console Application workspaces show the overall status for applications. In this table, all the rows for App1 are combined into one row with an overall status of Critical (worst status for the application).

Table 5. Overall status for sample Application Management Console application
Application Overall Status
App1 Critical

In the database the values of the Overall Status are stored not as text strings but as numerical values:

  • 0 = None
  • 10 = Good
  • 20 = Informational
  • 30 = Harmless
  • 40 = Warning
  • 50 = Minor
  • 60 = Critical
  • 70 = Fatal
Note: For ISM attributes, the Internet Services Monitoring Marginal state maps to the Response Time Warning state, and the Internet Services Monitoring Failed state maps to the Response Time Critical state.

Overall Time

The overall elapsed time for the application.

Packets Retransmitted

The number of packets retransmitted during the monitoring interval.

Page Title

The title of the web page.

Parent UUID

A unique identifier used with the Root UUID and Current UUID attributes to completely identify a specific subtransaction in your environment.

Password

Specifies the password that is used to logon to the realm in which the proxy server runs. You can enter an alphanumeric string with a maximum of 32 characters.

Path Arg

This attribute is for internal use only.

Pattern Arg

This attribute is for internal use only.

Percent Available

The percentage of transactions with a transaction status of Good or Slow, but not Failed. The sum of this attribute value and Percent Failed should total 100 percent. Any failure is considered important, so table cell for this attribute is displayed in the TEP with a green background only when the value for Percent Available is 100 percent. Any value less than 100 percent is displayed in the TEP with a red background in the table cell.

Percent Available (ISM)

The percentage of Internet Services Monitoring attempts that were either Good or Marginal, but not Failed. The sum of this attribute value and Percent Failed should total 100 percent.

Percent Client Errors

The percentage of requests with a status code between 400 and 499.

Percent Failed

The percentage of transactions whose requests were marked as Failed. This value is calculated by dividing Failed Requests by Total Requests and multiplying by 100%. The sum of this attribute value and the value of the Percent Available attribute should total 100%.

Percent Failed (ISM)

The percentage of Internet Services Monitoring attempts that failed.

Percent Good

The percentage of transactions whose requests were marked as Good. This value is calculated by dividing Good Requests by Total Requests and multiplying by 100%. The sum of this attribute value and the value of the Percent Slow attribute should equal the value of the Percent Available attribute.

Percent Good (ISM)

The percentage of Internet Services Monitoring attempts that were good.

Percent Informational

The percentage of requests with a status code between 100 and 199.

Percent Marginal (ISM)

The percentage of Internet Services Monitoring attempts that were marginal.

Percent of 403s

The percentage of HTTP requests with the status code 403.

Percent of 404s

The percentage of HTTP requests with the status code 404.

Percent of 500s

The percentage of HTTP requests with the status code 500.

Percent Redirections

The percentage of requests with a status code between 300 and 399.

Percent Server Errors

The percentage of requests with a status code between 500 and 599.

Percent Slow

The percentage of transactions whose requests were marked as Slow. This value is calculated by dividing Slow Requests by Total Requests and multiplying by 100%. The sum of this attribute value and the value of the Percent Good attribute should equal the value of the Percent Available attribute. Any value for this attribute that is greater than 0 percent is displayed with a yellow background in the TEP.

Percent Successes

The percentage of requests with a status code between 200 and 299.

Profile

The name of the Internet Services Monitoring profile. Note that this is different from the Application Management Configuration Editor profile name.

Profile Key

A unique name for the Application Management Console agent to identify the workspaces.

Property

Internal information about the current monitoring agent configuration. Use this attribute with the VALUE attribute.

Protocol

The user-defined networking protocol used for the TCP Transaction.

Rank

An internal calculation that sorts the transactions in order of highest to lowest importance for display in the workspace. Rank is calculated using a combination of values from the Importance, Number of Failed Requests, and Number of Slow Requests attributes. A larger numeric value suggests that the (higher ranked) transaction is more of a concern than a lower ranked transaction. Because the number is used for internal calculation, this value might not be consistent from release to release.

Realm Name

The name of the realm, typically the name of the server that hosts the website. You can enter an alphanumeric string with a maximum of 128 characters.

Realm Type

The type of server (Proxy or Realm) in the realm. Proxy means the server provides an indirect connection to a web server. Realm provide a direct connection to the realm.

Receive Bandwidth

The average number of kilobytes per second received by a server from a client during the current monitoring interval.

Redirections

The number of requests with a status code between 300 and 399.

Referrer URL

The URL from which the end user made a request.

Render Time

The total time taken, in seconds, to download, parse, and render the page from the user perspective.

Reply Ack Packet Count

The average number of acknowledgement packets from the server for requests made during the data interval. For instance data, this field is an absolute value, not an average.

Reply Bytes

The total number of bytes in each reply of the request during the data interval.

Reply kBytes

The total number of bytes in each reply of the request during the data interval.

Reply Packet Count

The average number of reply packets returned from the server for requests made during the data interval.

Request Ack Packet Count

The average number of acknowledgement packets in a request during the data interval. For instance data, this field is an absolute value, not an average.

Request Bytes

The total number of bytes in the request during the data interval.

Request kBytes

The total number of bytes in the request during the data interval.

Request Packet Count

The average number of packets in the request during the data interval. For instance data, this field is an absolute value, not an average.

Request Volume

The percentage (in 10 percent increments) of the current volume of requests compared to all of the previously recorded request volumes during the current Data Time Span.

The value of the Application Management Console Current Requests attribute is used to determine how the current request volume compares as an approximate percentage of all the previous volumes recorded during the current Data Time Span.

For example, consider the following table of values recorded for the Current Requests attribute every 5 minutes during the current Data Time Span:

Table 6. Samples of recorded Current Requests and the resulting overall Request Volumes over time
Time Current Requests Request Volume
12:00 157 Normal
12:05 222 Very High
12:10 189 Normal
12:15 193 High
12:20 311 Very High
12:25 201 High
12:30 167 Very Low
12:35 212 High
12:40 201 Normal
12:45 288 Very High
12:50 184 Low
12:55 201 Normal
13:00 179 Very Low
13:05 199 Normal
13:10 220 High
13:15 215 High
13:20 207 High
13:25 197 Low
13:30 201 Normal
The algorithm considers each current request in relation to the request volumes seen previously, and determines the resulting Request Volume using the relationship (A/B)* 100%, where:
  • A is the number of previously recorded Current Requests that are less than the current value.
  • B is the total number of previously recorded values for Current Requests.
The calculation of (A/B)*100% is compared to the values in the following table to arrive at the final determination for Request Volume:
Table 7. Request volume values
Value Percentage Range Name
0 0-19% Very Low
20 20-39% Low
40 40-59% Normal
60 60-79% High
80 80-100% Very High
1000 n/a None
For this example, the values for Request Volume are determined as follows:
  • At time 12:00, there is only one value recorded, so by default it is determined to be at a Normal request volume. This is represented in the database not as the text string Normal, but as the value 40, according to the previous table.
  • At time 12:05, the current value and the one previously recorded value are sorted into the ascending list, (157, 222). For the current value 222, there is one previously recorded value that is less than 222, so A=1, and there is one previously recorded value, so B=1. The ratio of A/B=1, or 100%, and the value for Request Volume is determined to be Very High. This is represented in the database by the value 80.
  • At time 12:10, the current value of 189 is sorted in ascending order with the two previous values, resulting in the ordered list (157, 189, 222). There is one previously recorded value that is less than 189, so A=1, and there are a total of two previously recorded values (157 and 222), so B=2. The ratio is then (1/2)*100% = 50%, or Normal.
  • Continuing further in time, at time 12:50, the current request value of 184 is sorted with the previous values in ascending order as (157, 167, 184, 189, 193, 201, 201, 212, 222, 288, 311). There are 2 previously recorded values that are less than 184, so A=2, and there are a total of 10 previously recorded values, so B=10, and the resulting Request Volume is calculated as 20%, or Low.

Repeating values: If the value of Current Requests is a duplicate of one or more previously recorded values, then the values are sorted into ascending order the current value is placed in the middle of the other like values in the list. For example, at time 12:55, the current request value of 201 is the same as two previously recorded values, at time 12:25 and time 12:40. The values are sorted in ascending order, resulting in the current value of 201 being placed in the middle of the three identical recorded values: (157, 167, 184, 189, 193, 201, 201, 201, 212, 222, 288, 311). In this case the calculation of Request Volume is modified to [(A+C)/B]* 100%, where C is one half the number of previously recorded values that are identical to the current value. In this case, there are 2 previously recorded values of 201, so C=1, and the Request Volume is calculated as [(5+1)/11]*100% = 54.54%, or Normal.

Normalizing over time: As more and more values for Current Requests are recorded during the current Data Time Span, the calculation of Request Volume is based on a larger sample of previously recorded values, resulting in a normalization of values over time. Note in the above example that early values of Request Volume include the extremes of Very High and Very Low, but by 13:30, the values are trending toward more frequent values of Low, Normal, and High).

After the current Data Time Span is completed, a new Data Time Span is started, and values of Current Requests that were recorded during the previous Data Time Span are no longer considered in the calculation of Request Volume.

Resolve Time

Reports the number of seconds (up to 3 decimal places) that was required to resolve the domain name of the URL. The resolve time is a part of the overall network time.

Response Time

The elapsed time, in seconds, required for the transaction to complete.

Response Time

Reports the end user response time status as Good, Fair, or Poor. This is displayed on the Application Management Console.

Retry Lag Time

The elapsed time, in seconds, to wait before attempting to retry a failed subtransaction or robotic script. For example, if the value of this attribute is set to 1, there will be a 1 second wait time between retries. As another example, if you set the number of retries to 3 with a lag time of 1, the software times out and generates an event when both of the following events take place:
  • The software tries the transaction four times (once as part of the playback, plus the three specified retries).
  • The software waits one second between retries.

Robotic Node

The name of the robotic node reported to the Application Management Console.

Robotic Script Name

The robotic script to play back for data collection. Enter an alphanumeric string of up to 128 characters or enter a pattern using one or more wildcard characters.

Root Transaction Name

For a subtransaction, this is the name of the associated main, or parent, transaction.

Root UUID

A unique identifier used with the Current UUID and Parent UUID attributes to completely identify a specific subtransaction in your environment.

Round Trip Time

The time it takes for a source computer to receive a one-byte TCP response after sending a one-byte TCP request packet.

Sample Time

The time and date (in Greenwich Mean Time) that the data was requested from the agent for storage or viewing. This information is displayed in the format, MM/DD/YY HH:MM:SS. For example, 01/03/07 12:05:03 means 12:05 p.m. on January 3, 2007.

Sample Timestamp

The date and time when the sample was collected.

Sampling Percent

The percentage of transactions to return that match a specified pattern during the data interval. For example, a value of 50 returns 50 percent of the matching transactions. This is a user-defined attribute.

Scope

The frequency at which status is reported (every 8 hours or every 5 minutes). Valid values are Summary_Status (every 8 hours) or Current_Status (every five minutes).

Scope

The amount of data that is returned (CURRENT means that only the last entry for each service is returned; ALL means that data for all intervals in the current summary interval (default 8 hours) is returned).

Script Name

The name of the robotic script to play back for data collection. Enter an alphanumeric string of up to 128 characters or enter a pattern.

Script Type

The type of robotic script that collected data for Robotic Response Time (CLI_Command_Playback, Rational_Performance_Tester, Rational_Functional_Tester, or Loadrunner (Mercury).

Send Bandwidth

The average number of kilobytes per second sent by a server to a client during the current monitoring interval.

Server

The name of the server that processed the transaction. This could be the hostname of the physical machine, the IP, or the Sysplex.

Server

The name or IP address of the server for the TCP Transaction.

Server Description

The description of the server that processed the web page requests.

Server Errors

The number HTTP requests with a status code between 500 and 599.

Server IP

The IP address of the server that originated the request. Restricting monitoring to one or more IP addresses is useful when you want to monitor transaction performance for a subset of users, such as a specific IT group in one of your internal corporate divisions. Enter an alphanumeric string up to 16 characters to specify the IP address or enter a pattern.

Server IP

The TCP/IP address of the server that sent or received the SSL Alert.

Server Key

The alias name of the subnode for the current server.

Server Path

The relative path name where the robotic script file is located on the file depot server.

Server Port

The TCP/IP port of the server that sent or received the SSL Alert.

Server Status

The application status at the client tier (Good, Fair, or Poor).

Server Time

The average timing of the server in seconds.

Server Time

The average timing of the server in seconds.

Service

The Internet Services Monitoring service name (examples: DNS, or HTTP).

Session

The name of the user session. The valid format is an alphanumeric string with a maximum of 32 characters.

Session Duration

The duration for the user session, in seconds.

Session End Time

The time that the user session ended.

Session Start Time

The time that the user session started.

Severity

The severity of the message (such as Informational, Warning, or Critical).

Severity

The severity of the SSL error (Warning or Fatal). A fatal error means the sender is disconnecting now. A warning error means the sender is willing to continue.

Situation Name

The name of the playback configuration profile that triggered the event.

Situation Status

The status of the transaction, based on the status of one or more default situations provided with ITCAM for Transactions. Note that user defined custom situations do not affect this attribute. If a recorded transaction triggers one or more default situations, this attribute contains the most severe status of the associated situations. This status is displayed in the Application Management Console.

Slow Requests

The number of recorded transactions that completed successfully, but whose response time was greater than or equal to the Minimum Response Time Threshold. This value is added to the values of the Good Requests and Failed Requests attributes to obtain the value of the Total Requests attribute.

Slow Requests

The number of recorded transactions that are slow during the current data interval.

Sort Order

The sort order.

Source Hostname

The source hostname for the transaction.

Source IP

The source IP for the transaction.

Source Node

The source node for the transaction (for internal use only).

Start Time

The time (during the last 8 hours) when the monitoring agent started collecting data. It uses the MM/DD/YY HH:MM:SS format, using GMT (Greenwich Mean Time). Example 01/03/08 12:05:03 indicates the aggregate value for the time period was 12:05 to 12:10 p.m. on January 3, 2008.

Start Time

The earliest interval start time for TCP data across all monitored components. This time is for internal use only and should not be used in situations.

Status Code

The response code associated with the transaction, depending on the monitoring agent. For ARM transactions, this attribute displays ARM response codes. For Web Response Time, it displays HTTP response codes. For CLI Playback, it displays the return code for the command that was executed, such $? or %ERRORLEVEL%.

Successes

The number of HTTP requests with a status code between 200 and 299.

Temp ID Post

The ID of the temporary file on the file depot server after a transfer.

Temp ID Pre

The ID of the temporary file on the file depot server before a transfer.

Terminated Connections

The total number of terminated TCP socket connections created during the current aggregate interval.

Timeout Period

The time, in seconds, to wait for a subtransaction or robotic script to respond before timing out and retrying. For example, if you set the number of retries to 3, a lag time of 1, and a timeout period of 30, the software times out and generates an event when all of the following events occur:
  • The subtransaction or robotic script is tried four times (once as part of the playback, plus three retries).
  • Each time, the subtransaction or robotic script does not respond within in 30 seconds.
  • The software waits one second between retries.

If the Timeout Period is too short, the process is terminated after retrying for the number of times specified in Retry Lag Time. When you define the timeout period, add a little extra time to the setting. For example, if your script takes 5 minutes to run, define a 6 minute timeout period to include a 1 minute buffer (enter 360 to define a 6 minute timeout period).

Timestamp

A timestamp that indicates the beginning of the aggregate time for the record, expressed in localized format (such as MM/DD/YY HH:MM:SS). For example, 01/03/07 12:05:03 indicates the aggregate value for the time period was 12:05 to 12:10 p.m. on January 3, 2007. In instance tables this value represents the exact time that the transaction completed.

Timestamp (ISM)

A timestamp indicating the time when Internet Services Monitoring data is received by the Application Management Console, expressed in Greenwich Mean Time (GMT), in the format of the local settings.

Timestamp

A timestamp that indicates the start of the current summary interval.

Time Zone

The time zone in which the web server operates.

Total Bytes

The total number of bytes transferred for all request during the time period.

Total kBytes Received

The total number of kilobytes of data received by the server during the current aggregate interval.

Total kBytes Sent

The total number of kilobytes of data sent by the server during the current aggregate interval.

Total Connect Time

The average elapsed time, in seconds, from the time a request is made to when the browser successfully connects to the web server. For instance data, this field is an absolute value, not an average.

Total DNS Time

The time, in seconds, required to look up the Domain Name System (DNS) address of the website.

Total Download Time

The amount of time (in hours, minutes, seconds, and milliseconds) elapsed between connecting with the web server and downloading the web page. If the transaction is interrupted or canceled before the page is downloaded, the elapsed time from the connection to the interruption is reported.

Total Failed Users

The total number of unique users experiencing Failed performance (a failed transaction). For example, if the user at IP address 128.1.2.3 experiences a Failed performance for a single WRT transaction, and the same user later experiences Failed performance during the same time period, that user is counted only once in both the Failed count and the All count. For the attribute groups that monitor a specific time interval, the value is the actual count for the time period. For all of the Current Status and Summary attribute groups, the values are averages (see Average Failed Users).

Total Good Users

The total number of unique users experiencing Good performance (not a failed transaction and not slower than the minimum response time threshold) for the time period. For example, if the user at IP address 128.1.2.3 experiences a Good performance for a single Web Response Time transaction, and the same user experiences Good performance again during the same time period, that user is counted only once in both the Good count and the All count. For the attribute groups that monitor a specific time interval, the value is the actual count for the time period. For the Current Status and Summary attribute groups, the values are averages (see Average Good Users).

Total Header Request Resolve Time

The average elapsed time, in seconds, that is required to resolve all header requests. For instance data, this field is an absolute value, not an average.

Total Header Requests Count

The total number of header requests that return an HTTP response code of 304, or that return no content.

Total kBytes

The total number of bytes transferred for all requests during the time period.

Total Object Count

The total number of objects embedded in a web page for the time period. For the attribute groups that monitor a specific time interval, the value is the actual count for the time period. For the Current Status and Summary attribute groups, the value is an average.

Total Object Size

The total size of all objects embedded in the web page for the time period. For the attribute groups that monitor a specific time interval, the value is the actual count for the time period. For the Current Status and Summary attribute groups, the value is an average.

Total Packets Received

The total number of IP packets received by the server during the current aggregate interval.

Total Packets Sent

The total number of IP packets sent by the server during the current aggregate interval.

Total Requests

The total number of recorded transactions observed during the monitoring interval. The value for this attribute is the sum of the Good Requests, Slow Requests, and Failed Requests attributes.

Total Requests (ISM)

The total number of Internet Services Monitoring attempts. The value for this attribute is the sum of the Good, Marginal, and Failed attempt attributes.

Total Resolve Time

The time, in seconds, required to resolve the domain name of the website.

Total Server Response Time

The difference between the request finish time and the request start time (request finish time – request start time). If there are multiple requests run in a collection period, the Total Server Time is the sum of all the requests.

Total Slow Users

The total number of unique users experiencing slow performance (not a failed transaction, but slower than the minimum response time threshold) for the time period. For example, if the user at IP address 128.1.2.3 experiences a slow performance for a single WRT transaction, and the same user later experiences slow performance again during the same time period, that user is counted only once in both the Slow count and the All count. For the attribute groups that monitor a specific time interval, the value is the actual count for the time period. For the Current Status and Summary attribute groups, the values are averages (see Average Slow Users).

TotalTime

The total amount of time for the Internet Services Monitoring attempt.

Total Transactions

The total number of request and response sequences observed by the monitoring agent during the current aggregate interval.

Total Transaction Time

The average of the TCP transaction time during the aggregate monitoring interval, that is, the time between the last reply packet and the first request packet for a transaction.

Total Users

The total number of unique users for the time period. A user that experiences a Good, Failed, or Slow performance for a single Web Response Time transaction is counted once. For attribute groups that monitor a specific time interval, the value is the actual count for the time period. For the Current Status and Summary attribute groups, the values are averages (See Average Users).

Transaction

A user-defined name of the monitored transaction. When defining a transaction pattern , if you select to aggregate by pattern, then the transaction that matches the defined pattern is replaced by the Transaction Name and aggregated together with all other unique transactions that also match the defined pattern.

Transaction Name

The transaction name reported to the Application Management Console.

Transaction Pattern

The pattern for specifying the names of specific transactions to monitor

Type

Displays the type of data collector (ARM, ROBOT, or WRM) that collected the data record. Valid values are:
ARM
Indicates Robotic Response Time
ROBOT
Indicates Robotic Response Time
WRM
Indicates Web Response Time

Universal Messages

This is an IBM Tivoli Monitoring attribute group. Refer to the IBM Tivoli Monitoring product documentation for more information.

Universal Time

This is an IBM Tivoli Monitoring attribute group. Refer to the IBM Tivoli Monitoring product documentation for more information.

Updated Time

The start time of the most recent interval for TCP data across all monitored components. This time is for internal use only and should not be used in situations.

URL

The URL of the monitored web page.

URL Anchor

The anchor text displayed for the hyperlink of the monitored web page.

URL File

The URL of the file in the monitored web page.

URL Hostname

The TCP/IP hostname of the URL.

URL Path

The URL path to the file on the server hosting the web page.

URL Query String

The string of a URL that contains the search parameters when a dynamic web site is searched.

User

Specifies the user name for the user session. The valid format is an alphanumeric string with a maximum of 64 characters.

User Logins

The number of user logins. The valid format is an integer.

User Name

The name of a valid user for the realm in which the proxy server runs. The valid format is an alphanumeric string with a maximum of 32 characters.

Value

Internal information about the current monitoring agent configuration, used with the Property attribute.

Value

The value of the property that is specified by the Key Name attribute. For example, if Key Name is URL, then this attribute specifies the value of the URL.

Violation Data

The value of the data that caused the event violation.

Web Server

The application status at the web server tier (Good, Fair, or Poor).

Xfer Mode

Indicates if the Application Management Configuration Editor is trying read a file (R), save a file (S), or delete a file (D).

Xfer State Post

The state of the file transfer after it completes (B = Begin, W = Working, C = Complete, F = Failed).

Xfer State Pre

The state of the file transfer before it begins (B = Begin, W = Working, C = Complete, F = Failed).