Chatee ahora con Soporte
Chat con el soporte

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 Processing Time

How much time does the back end spend processing the command?

The Command Processing Time metric includes all the time spent processing the command at the back end. This time includes the Command Initial Response Time.

The following example is a common interaction between a client and server, where the data being sent by the server does not fit in a single packet.

Here, the arrows represent packets crossing the network. The first packet carries the request from the client to the server. The two packets from the server carry the response containing the HTML results from running request.asp (3000 bytes long).

As shown in the previous section, Command Initial Response Time is calculated by finding the time difference between the request packet arriving at the server, and the response packet leaving the server. Command Processing Time includes this initial response time (TimeB – TimeA) plus the time taken to transmit all of the response packets (TimeC – TimeB).

Command Processing Time = TimeC – TimeB + Command Initial Response Time
or
Command Processing Time = TimeC – TimeA

The following example shows a more complicated interaction between a client and server, where the response data leaving the server must be sent in more than one burst. Each burst of data consists of two data packets. For more information, see Understanding server bursts.

Here, the server needs to wait for an acknowledgement (ACK) from the client between bursts. Once it receives an ACK for the first burst, it can send the next burst of data (C).

Since the Command Processing Time metric deals with what occurs at the back end, it includes the Command Initial Response Time, but does not include time required client-side activities (i.e., creating and sending an ACK). Thus, Command Processing Time here is command processing time 1 + command processing time 2.

This calculation holds true for commands that return even more content shown in the above example. All this means is there will be more bursts sent from the server, in which case, the processing time for each will be measured and added together.

The TCP protocol limits how much data the server can send in a burst without receiving an acknowledgement (ACK) from the client. This maximum amount of data the server can send is called the TCP window size. This window size is negotiated between the client and server when the TCP connection is established, and is used for congestion control on the network. (In the example used in the previous section, the TCP window size was 3000 bytes.)

As the server sends data, it reduces the TCP window size by the amount of data that was sent. As the client ACKs data, the server can increase its current window size by the amount of data ACKed. So long as the server continually receives ACKs from the client, its TCP window will remain “open,” allowing it to continue to send data. However, if there is congestion or delays on the network, the server will continue to send data until its window size is 0, which means the window is “closed.” At that point, the server must stop sending data and wait for an ACK from the client.

Obviously, larger windows allow the server to burst more data at once, but also increase the chance for congestion which can lead to dropped packets and the server needing to resend data. Smaller windows decrease the chance for causing congestion but result in less efficient communication between client and server.

Command Client Time

How much time does the client spend acknowledging a portion of the response sent from the back end?

While the Command Processing Time metric, and by extension, Command Initial Response Time, shed light on the timings at the back end, the Command Client Time metric determines how much time is spent at the client side during client-server communication with multiple bursts.

The following example represents a common interaction between a client and server, in which a large file, sent by the server, is separated into and sent as several packets (1500 bytes). Whenever data is sent by the server, the TCP protocol requires the client to routinely send acknowledgements (ACK) after it has received two full data packets.

Here, the arrows represent packets crossing the network:

In the above example:
Command Client Time = client-side time 1 + client-side time 2

The Client Time portions shown in the diagram can be broken down as follows:

Thus, Command Client Time is the sum of all the Client Time delays that occur between each burst of server data.

Command Completion Time

How much time is required to receive, process, and transmit all response data back to the client for a given request?

The three previous sections explained the calculations behind the initial response time of the server, the server request-processing time, and the client acknowledgement time. The Command Completion Time metric is the sum of all three of these actions:

(Note that Command Processing Time includes Command Initial Response Time.)

There may be cases where there is no Command Client Time, in which case the Command Completion Time is simply the Command Processing Time. Consider the following example.

Here, as described for Command Processing Time, there is only one request packet, and although there are two response packets, there is still no time spent on the client side.

Command Completion Time includes the entire delay from when the first packet in the client’s request arrives until the last packet in the server’s response is sent. Here, the delay is equal to the Command Processing Time.

The next example demonstrates how Command Client Time is incorporated into Command Completion Time. Consider the following example.

In this example, the total Command Processing Time is split because the client-bound data is sent over more than one burst (TimeB – TimeA, and TimeD – TimeC). The Command Client Time is the total amount of time required for the client to acknowledge the first burst, which includes both travel time and client-side processing time (TimeC – TimeB).

Again, Command Completion Time includes the entire delay from when the first client packet in the request arrives at the server (A), until the last packet in the server’s response is sent (D). This includes all server-side processing time (i.e., Command Processing Time 1 + Command Processing Time 2), as well as all client time (i.e., Command Client Time).

Command Network Latency

The concept behind the Command Network Latency metric is very similar to the Page Network Latency metric. For a detailed explanation that covers both metrics, see Network Latency.

Documentos relacionados