Chat now with support
Chat with Support

Foglight Experience Monitor 5.8.1 - Metric Reference Guide

Foglight Experience Monitor metric categories
General metric categories Application-oriented categories Service-oriented categories Web services category Content-oriented categories Infrastructure-oriented categories Types of metrics How standard metrics are calculated End-User Access Speed Network Latency Instrumented metric: Load Time Time frames in which metrics are viewed
Metric definitions
Non-system category metrics
Access Speed Access Speed Distribution Alarm Application Time Cipher Suite Not Found City Clicks per Session Client IP Command Byte Volume - Server Command Byte Volume - User Command Client Time Command Completion Time Command Count Command Data Size - Server Command Data Size - User Command Initial Response Time Command Initial Response Time Distribution Command Network Latency Command Processing Time Command Processing Time Percentile Command Processing Time Service Level Command Timeout Count Component List Size Connection Closed Count Connection Count Connection Duration Connection Established Count Connection Open Wait Count Connection Reset Count Connection Timeout Count Duration End-to-End Time for Dialup Users (0-56k) End-to-End Time for ISDN Users (56k-128k) End-to-End Time for Low-End Broadband Users (128k-384k) End-to-End Time for High-End Broadband Users (384k-728k) End-to-End Time for T1/Lan Users (> 728k) End-to-End Time Service Level Error Count (HTTP 4xx Client Errors) Error Count (HTTP 5xx Server Errors) Fault Actor Fault Code Fault Detail Fault String Fault Subcodes Field Out of Range Hit Count Hit End-To-End Time Hit Redirect Ratio Hit Size Incomplete SSL Key Invalid SSL Content Invalid SSL Handshake Type Invalid SSL Key Invalid SSL Record Length Invalid SSL State Invalid SSL Version Number IP Packet Byte Volume - Server IP Packet Byte Volume - User IP Packet Count - Server IP Packet Count - User IP Packet Size - Server IP Packet Size - User ISP Load Time Load Time Percentile Login Name Missing Reusable Secret Missing SSL Key Other Requests Page Access Speed Distribution Page Client Time Page Connection Count Page Download Attempts Page Download Size Page Element Count Page End-to-End Time Page End-To-End Time Distribution Page End-To-End Time Percentile Page Exit Count Page Network Latency Page Peak Count per Second Page Processing Time Page Processing Time Distribution Page Processing Time Percentile Page Redirect Ratio Page Stop Count Page Stop Rate Page Stop Time Page Think Time Page Timeout Count Page Views Path Count Path Duration Path End-To-End Time Path End-to-End Time Percentile Processing Load Percentage Processing Time Service Level Referrer Request Code Count Response Code Count Service Abort Count Service Client Time Service Count Service Duration Service End-to-End Time Service End-to-End Time Distribution Service End-to-End Time Percentile Service Network Latency Service Peak Count per Second Service Processing Load Percentage Service Processing Time Service Processing Time Distribution Service Processing Time Percentile Service Processing Time Service Level Service Request Count per Second Service Started Count Service Think Time Service Timeout Count Session Count Session Key Site Stickiness SOAP Operation Client Time SOAP Operation Completion Time SOAP Operation Completion Time Distribution SOAP Operation Consumer Overhead Ratio SOAP Operation Count SOAP Operation End-To-End Time SOAP Operation End-to-End Time Distribution SOAP Operation End-to-End Time Percentile SOAP Operation Failure Count SOAP Operation Initial Response Time SOAP Operation Network Latency SOAP Operation Peak Count per Second SOAP Operation Processing Time SOAP Operation Processing Time Distribution SOAP Operation Processing Time Percentile SOAP Operation Provider Overhead Ratio SOAP Operation Success Count SOAP Operation Success Ratio SOAP Operation Think Time SOAP Operation Timeout Count SOAP Transaction Abort Count SOAP Transaction Client Time SOAP Transaction Completion Time SOAP Transaction Completion Time Distribution SOAP Transaction Count SOAP Transaction Duration SOAP Transaction End-to-End Time SOAP Transaction End-to-End Time Distribution SOAP Transaction End-to-End Time Percentile SOAP Transaction Initial Response Time SOAP Transaction Network Latency SOAP Transaction Peak Count per Second SOAP Transaction Processing Time SOAP Transaction Processing Time Distribution SOAP Transaction Processing Time Percentile SOAP Transaction Processing Time Service Level SOAP Transaction Request Peak Count per Second SOAP Transaction Think Time SOAP Transaction Timeout Count SSL Memory Error Step Started Count Step Completion Count Step Abort Count Step Timeout Count Subnet Success Ratio Success Ratio (with Client Errors) Success Ratio (with Server Errors) TCP Command Client Time TCP Command Completion Time TCP Command Count TCP Command Initial Response Time TCP Command Initial Response Time Percentile TCP Command Network Latency TCP Command Processing Time TCP Connection Open Peak Count per Second TCP Queue Size TCP Control Segment Byte Volume - Client TCP Control Segment Byte Volume - Server TCP Control Segment Count - Client TCP Control Segment Count - Server TCP Control Segment Size - Client TCP Control Segment Size - Server TCP Data Segment Byte Volume - Client TCP Data Segment Byte Volume - Server TCP Data Segment Count - Client TCP Data Segment Count - Server TCP Data Segment Size - Client TCP Data Segment Size - Server TCP Duplicate Resend Segment Byte Volume - Client TCP Duplicate Resend Segment Byte Volume - Server TCP Duplicate Resend Segment Count - Client TCP Duplicate Resend Segment Count - Server TCP Duplicate Resend Segment Size - Client TCP Duplicate Resend Segment Size - Server TCP Fragmented Segment Byte Volume - Client TCP Fragmented Segment Byte Volume - Server TCP Fragmented Segment Size - Client TCP Fragmented Segment Size - Server TCP Fragmented Segment Count - Client TCP Fragmented Segment Count - Server TCP Invalid Checksum Segment Byte Volume - Client TCP Invalid Checksum Segment Byte Volume - Server TCP Invalid Checksum Segment Size - Client TCP Invalid Checksum Segment Size - Server TCP Invalid Checksum Segment Count - Client TCP Invalid Checksum Segment Count - Server TCP Payload Byte Volume - Client TCP Payload Byte Volume - Server TCP Resend Segment Byte Volume - Client TCP Resend Segment Byte Volume - Server TCP Resend Segment Count - Client TCP Resend Segment Count - Server TCP Resend Segment Size - Client TCP Resend Segment Size - Server TCP Segment Byte Volume - Client TCP Segment Byte Volume - Server TCP Segment Count - Client TCP Segment Count - Server TCP Segment Size - Client TCP Segment Size - Server TCP Timeout Count - Syn TCP Timeout Count - Idle TCP Timeout Count - Half Open TCP Urgent Segment Byte Volume - Client TCP Urgent Segment Byte Volume - Server TCP Urgent Segment Count - Client TCP Urgent Segment Count - Server TCP Urgent Segment Size - Client TCP Urgent Segment Size - Server Unexpected Client Hello Message Unexpected Server Hello Message Unknown Key Exchange Unload Time Unload Time Percentile User Agent User Count User Stickiness
System category metrics
Agent Memory Consumption Warnings Agent Restarts Baseline Partition Size Backup Errors Checksum Errors Client Segments Count Client Segments Missing Client Segments Missing Rate Communication Errors Connection Errors Connections Started Connections Dropped CPU1 Temperature CPU2 Temperature CPU Core 1 Utilization CPU Core 2 Utilization CPU Core 3 Utilization CPU Core 4 Utilization CPU Core 5 Utilization CPU Core 6 Utilization CPU Core 7 Utilization CPU Core 8 Utilization CPU Utilization Database Load Errors Database Load Time Database Partition Usage Database Records Loaded Datastore Inode Usage Datastore Partition Usage Day Partition Size Excessive Data Volume FxV Bytes Transmitted FxV Discards FxV Hits Transmitted Hour Partition Size Log Partition Usage Memory Consumption Warnings Memory Utilization Metric Table Entries Metric Table Size Minute Partition Size Monthly Partition Size OS Partition Usage Packet Drop Rate Packet Errors Packet Errors - Port 1 Packet Errors - Port 2 Packet Errors - Port 3 Packet Errors - Port 4 Packet Errors - Port 5 Packet Errors - Port 6 Packet Errors - Port 7 Packet Errors - Port 8 Packets Captured Packets Captured – Port 1 Packets Captured – Port 2 Packets Captured – Port 3 Packets Captured – Port 4 Packets Captured – Port 5 Packets Captured – Port 6 Packets Captured – Port 7 Packets Captured – Port 8 Packets Dropped Packets Dropped – Port 1 Packets Dropped – Port 2 Packets Dropped – Port 3 Packets Dropped – Port 4 Packets Dropped – Port 5 Packets Dropped – Port 6 Packets Dropped – Port 7 Packets Dropped – Port 8 Packets Processed Packets Processed – Port 1 Packets Processed – Port 2 Packets Processed – Port 3 Packets Processed – Port 4 Packets Processed – Port 5 Packets Processed – Port 6 Packets Processed – Port 7 Packets Processed – Port 8 RAID Array Degraded Relation Table Entries Relation Table Size Resource Table Entries Resource Table Size SiteMinder Errors Server Segments Count Server Segments Missing Server Segments Missing Rate SOAP Error Rate SOAP Errors SOAP Message Count SOAP XML Errors SSL Connection Errors SSL Connections Released SSL Connections Started SSL Connection Error Rate Swap Partition Usage System Temperature Tmp Partition Usage Total Table Size Value Count Table Entries Value Count Table Size Weekly Partition Size

Command Timing Metrics summary

The following example summarizes how the command timing metrics are calculated, using the simplest interaction between a client and server (i.e., a request and response that each fit in a single packet).

Client-server interaction and timing calculation is as follows:

The metrics are calculated as follows:

The time between the server-side arrival of the request packet and the transmission of the first response packet:

The sum of all server-side processing times. This normally includes the Command Initial Response Time as well as any further server-side delays before additional data is sent to the client. Since, in this example, the response fits in a single packet:

The time between the server-side transmission of a block of response data, and the reception of the client ACK. Since, in this example, no ACK is sent by the client, Command Client Time = 0.

The time between the server-side arrival of the first packet in the request and the transmission of the very last response packet, or:

In this example, since there is no Command Client Time, the Command Completion time is the Command Processing Time, or TimeC – TimeB.

This is an estimate of the two network delays that cannot be measured directly:

For more information on how calculations are performed for this type of metric, see Network Latency.

The following example summarizes how the command timing metrics are calculated in a common interaction between a client and server (for instance, a large file is sent by the server, and is subsequently sent to the client across multiple packets).

Client-server interaction and timing calculation is as follows:

10
Step 6 through Step 9 are repeated until all data has been sent to the client.

The metrics are calculated as follows:

The time between the server-side arrival of the request packet and the transmission of the first response packet:

The sum of all server-side processing times:

Note that the first Command Processing Time includes the Command Initial Response Time.

The time between the server-side transmission of a block of response data, and the reception of the client ACK:
TimeG – TimeD

During this time, the client waits to receive, processes, and acknowledges the received data.

The time between the server-side arrival of the first packet in the request and the transmission of the very last response packet:

Note that this calculation applies to the transmissions shown in previous diagram.

For more information on how calculations are performed for this type of metric, see Network Latency.

Exceptions

Some HTTP requests do not receive a valid response when the following occurs:

When no-response hits are received do the following:

When no-response hits are received do not:

The system does not include these no-response hits since they would skew all of the timing metrics to the downside if they were included. The system also does not update the timing metrics if the hit was a redirect. Redirects (for example 304 - Not Modified) are very fast, and occur quite often. If these values were included in the performance metrics, they would lower value. If you would like to include redirects you can uncheck Exclude redirects from metric calculations on the Configure > Monitoring > URLs> Advanced Options page.

Page Timing metrics

The main page timing metrics are:

These metrics provide performance information about different parts of a page download. A page consists of one or more hits, each of which is identified by a URL.

The content for each hit is requested through a GET or POST command for the specific URL. Consequently, most page timing metrics are at least partially derived by the underlying command timing metrics (as described on Command Timing metrics).

A page download consists of the main hit (i.e., the first hit requested), plus any hits embedded in the first hit. These sub-hits can consist of one or more of the following types of objects:

Often, the page and all of its hits is called a complete unit of work. Pages are uniquely identified by the URI for the main hit in the page download.

From the combined perspective of the client and server, a page download begins when the end user clicks a link on a page in their web browser:

This parallel downloading of hits happens with all modern web browsers when requesting the contents of any non-trivial page, and maximizes utilization of the client’s access pipe.

In the following example, the web browser opens three connections to retrieve all the content required for the page download.

To reiterate, the hits were downloaded in the following order:

The following sections describe the various ways in which the client and server can interact during a web session, and how the page timing metrics are measured.

Page End-To-End Time

How long does it take to download a full page?

The Page End-To-End Time metric includes the time required to request and send back all the hits of a page. This includes the original request from the end user for a URI, plus all frames, images, applets, style sheets, script files, and any other content that may be embedded or invoked within that original URI.

Although timing the initial request and the sending of the final hit is straightforward in theory, there are some factors to consider. Examine the following example.

The page end-to-end time starts when the user sends a command to the server requesting main.html (A). The page end-to-end time ends when final part of the response, representing the last hit, arrives at the client (D).

Since the appliance’s perspective is from the back-end, it can only directly measure when hits arrive at the server, or responses are sent from the server. In the above example, this means that the User Performance Application:

In order to account for the times taken by the request or responses that cannot be measured directly, the appliance uses a Round-Trip Time value to estimate them. During user sessions, the appliance always maintains a Round-Trip Time value in order to provide an accurate estimate in situations such as this. For more information about this metric, see Network Latency.

In the above example, in order to account for the time taken for a request to move from client to server (B – A), or the final response to move from server to client (D – C), the appliance adds one half of the current Round-Trip Time estimate for each case. These two delays added together equal the current RTT.

This approach gives the following calculations for Page End-To-End Time:

where

Page Completion Time =
time when request for first hit
arrives – time when last packet of last hit departs

Related Documents