Chat now with support
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

How Network Latency is used to calculate other metrics

The calculations for metrics such as Page End-To-End Time, Page Client Time, and End-User Access Speed include the use of the Network Latency metric. This metric is valuable in these calculations because it helps estimate the network delays that cannot be directly measured by the appliance from its server-side position on the network.

Calculating Peak Count metrics

Network events are highly variable. Network events can arrive in tightly packed groups (also called bursts) followed by long delays before another burst of events occur. The size of these bursts are significant because they put the most load on the monitored network’s infrastructure. The appliance measures these events to determine the largest burst size that can occur using a group of metrics referred to as Peak Counts.

These metrics measure the largest number of events that can occur during a 1-second interval. Peak Count metrics in the appliance include the following events:

The methodology for calculating all of these metrics is the same. All that differs is which events are being tracked.

For example:

Service Start Peak Count tracks peak count of service start events.

Service Peak Count tracks peak count of service completion events.

The method for calculating any peak count metric follows:

It is possible that a burst of events could span the one-second interval. This could possibly result in a peak count that is less than the real maximum burst size. This issue is mitigated, however by the large number of samples (300) that are taken during a 5-minute interval. The large number of samples should ensure that an accurate measurement of the largest 1-second burst size is captured.

Instrumented metric: Load Time

How is the Load Time instrumented metric calculated when using an external Content Delivery Network (CDN)?

In a typical page request for main.html on in-house web servers, the calculation of Page End-to-End Time starts when the server receives the request, includes time spent on all in-house servers, and ends when the server responds. For more information, see Page End-To-End Time.

When an in-house web server hands off a request to a CDN server, Foglight Experience Monitor cannot track the time spent on the request by the CDN servers. Therefore, the reported Page End-to-End Time becomes the time the in-house web server spends on the initial request for main.html before passing it on to a CDN server. This results in a partial page response.

The solution to the partial page response is instrumentation. Foglight Experience Monitor can report on CDN server time if customers instrument their web pages to run a JavaScript file called quest-fxm.js provided with Foglight Experience Monitor. With instrumentation, the Load Time metric misses the initial request and partial response time, but it does provide an alternative means to measure page loading time for a page that is using CDN services. The result is similar to Page End-to-End Time, but not exactly the same (because the metrics are measuring different events).

The Load Time metric records the length of time an instrumented page needs to load into the browser. By default, it uses the onLoad Javascript event. The time is recorded from the moment when the instrumentation starts, until the onLoad event occurs. The Load Time is updated with the value of the load metric tag, which is sent to the instrumentation URL.

For instrumentation instructions, see “Instrumenting web pages” in the Foglight Experience Monitor Installation and Administration Guide.

Time frames in which metrics are viewed

Once installed and configured, the appliance continuously monitors web traffic and performs analyses in real-time. The metrics generated by the appliance are organized into time series. A time series defines the time-based granularity of the metric. For example, a metric may reflect every event in the 8:00 AM hour, every event that occurred last Thursday, or every event that occurred last week.

The length of time data is kept for each time series depends on the size of the time intervals in the time series. Larger intervals are kept longer than smaller intervals (for example, monthly data is kept longer than real-time).

Real-time, hourly, daily, weekly, monthly are considered time series because once an interval in the time series is complete, all metrics for all resources in the current interval are saved. After the data is saved, no new updates can be made to the metrics in that interval. A time interval is considered complete when the next event has a timestamp for the following time interval. The metrics for all resources in the current time interval are stored in the database.

There are five different time series tracked by the system: real-time, hourly, daily, weekly, and monthly.

This time series contains the smallest intervals of the different time series. Real-time intervals are five minutes long. For each hour, 12 new intervals are created. Intervals are labeled by their starting time. For example, the real-time interval that spans 08:00.00 to 08:04.59 is labeled as 08:00. The data for real-time intervals is kept for one week.

Time intervals in this time series are 60 minutes long. For each day, 24 new intervals are created. Intervals are labeled by their starting time. For example, the hourly time interval that spans 13:00 to 13:59.59 is labeled 13:00. The data for hourly intervals is kept for one month.

Time intervals in this time series are 24 hours long. For each week, seven new intervals are created. Intervals are labeled by their common day of the week abbreviation (Sun, Mon, Tue, Wed, Thu, Fri, Sat). The interval boundary for a day is set at 00:00.00 till 23:59.59. The data for daily intervals is kept for one month.

Time intervals in this time series are seven days long (each day is 24 hours long). During a year, 52 new intervals are created. The interval boundary for a week goes from Sunday at 00:00.00 till Saturday at 23:59.59. Intervals are labeled by the starting date for each week (for example, 12/22). The data for weekly intervals is kept for two months.

Time intervals in this time series vary in length from 28 days to 31 days long (each day is 24 hours long). During a year, 12 new intervals are created. The interval boundary for a month goes from 00:00.00 on the first day of the month to 11:59.59 on the last day of the month. Intervals are labeled by the common abbreviation for each month (for example, Jan, Feb, Mar). The data for monthly intervals is kept for 12 months.

 

Documentos relacionados