Chatee ahora con Soporte
Chat con el soporte

Foglight APM for Real User Experience 5.9.9 - User Guide

Getting started with Foglight APM Monitoring transactions Viewing real user activity from a geographical perspective Assessing real user experiences during key sequences Monitoring the performance of web sites and endpoints Searching APM data Replaying sessions, hits, and sequences Visualizing search results Creating custom drag-and-drop dashboards APM tile and view reference

Investigating a web site or endpoint

When you need more information than the Busiest view or Alarm view provides, select the site or endpoint of interest. The Results view changes to show a set of charts containing hit performance, page performance, warnings, and errors for the time range. You can use these charts to discover whether the average times reflects a consistent level of performance, or if the performance is uneven. From here, even more data is available by clicking a chart or the Explore button.
Many things can cause a sudden change in performance or errors. Here are a few possibilities:
•
A page is deleted but there are still references to it, causing page errors.
•
Changes to an application’s code causes slower responses to hit requests.
•
An ISP is experiencing higher than normal volume resulting in higher client times.
•
Web servers are temporarily down in a server farm, and the remaining servers are overloaded.
•
A change occurs in the infrastructure, such as a vMotion® that moves an application to a less responsive host.
 
* 
NOTE: For descriptions of the metrics in this and other dashboards, search the online help using the metric name. For hit errors and warnings, look up “Status Metrics.”
To investigate a web site:
1
Click a site|endpoint.
Charts reflect performance for the time period.
 
Table 7. Investigating a web site or endpoint
View
Description
Page Performance
For pages, displays time spent on the server side, the network, and the client side.
Hit Performance
For hits, displays time spent on the server side, the network, and the client side.
Errors
Displays errors on hits that occur during the time range.
Warnings
Displays warnings on hits that occur during the time range.
Alarms
Displays alarms for this site|endpoint, if any.
2
Look for clues to issues, such as:
•
A sudden change in performance over the time range.
•
An onset of warnings and errors where none existed in previous time ranges.
•
Consistently higher than expected values for one of the metrics.
3
If you need more details to understand the issue, click Explore.
A dashboard opens for the selected site|endpoint.
4
Review overall performance in the Summary tab. The Summary tab is similar to the preceding view, but adds the following metrics for the time period: End to End Time, Capture Rate, and Volume.
5
To investigate hit performance, click the Hits tab. The Hits tab displays detailed hit performance and hit volume metrics plus request and response code metrics for the time period.
 
Table 8. Hits tab views
Views
Purpose
Hit Performance
Displays metrics that contribute to overall hit performance. This chart includes the initial response time.
Hit Volume
Displays metrics that contribute to the overall hit volume, including the size of headers and content for both requests and responses.
HTTP
Displays the request methods and response codes issued for hits on this site|endpoint.
Warnings and Errors
Displays warnings and errors for the hits associated with this site|endpoint.
Alarms
Displays alarms for this site|endpoint, if any.
6
To investigate page performance, click the Page tab. The Page tab displays detailed page performance and page volume metrics for the time period.
 
Table 9. Page tab views
Views
Purpose
Page Performance
Displays additional metrics that contribute to overall page performance, including redirects and incomplete downloads.
Page Volume
Displays additional metrics that contribute to the overall page volume, including the size of headers and content for both requests and responses.
Warnings and Errors
Displays warnings and errors for the pages associated with this site|endpoint.
Alarms
Displays alarms for this site|endpoint, if any.
7
To return to the previous dashboard, click Web Sites and Endpoints in the breadcrumb trail.

Troubleshooting an excessive number of monitored web sites

If you have an excessive number of web sites reported in this dashboard, consider aggregating data capture for similar sites. For example, if you attribute the data collected for alias sites to the primary site, then only the primary site appears in this dashboard. In general, data aggregation makes the data more manageable and more meaningful in all dashboards.
To define data aggregations, an APM Administrator creates domain rules. In a troubleshooting scenario, where you want a quick way to aggregate data for a large number of similar sites, use a regular expression that matches multiple sites and map the sites to a fictitious (or real) domain name. For information about defining domain rules, see “Managing domain rules” in the Foglight APM Administration and Configuration Guide.
 
* 
NOTE: Only data captured after the domain rule is created is aggregated. Historical data is not affected.
Example
Consider a scenario where all sites of interest are identified in the dashboard by domain names, but Foglight APM is also monitoring a proliferation of IP addresses that are of little or no interest. The following regular expression matches all IP addresses and aggregates them under a single fictitious domain called myOtherSites.com. This rule eliminates the “noise” generated by all the extraneous sites and allows you to focus on what really interests you.
Find: \b\d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3}\b
Replace: myOtherSites.com
 
 

Searching APM data

Foglight captures, decrypts, analyzes, and stores a vast amount of data about how real users navigate your web sites and applications, the performance of the web servers and application servers in your infrastructure, and the performance of Java™ applications and .NET® applications. This data is stored as details in the Archiver database.
You can see the details when you drill down from the top-level dashboards (Geographical Perspectives, Sequence Explorer, and Web Sites and Endpoints dashboards). In the top-level dashboards, you view aggregated metrics derived from the details. For example, in the Sequence Explorer, you see exit counts that represent a total for all users who performed the same sequence of steps. When you drill-down on a tile, you can navigate to the expanded details in a Search dashboard. So for the sequence, you can drill down to the captured sequences to evaluate individual user experiences.
You may come across situations where you want to search the Archiver database directly using your own search criteria. For example, if a real user reports having issues with your web site, you can search for the session and replay it to see what your user experienced. Each type of search has its own dashboard and offers a simple search and an expert search. You can save searches and rerun them later. You can also run the last search and clear search results.
From search results, you can replay a hit, sequence, or session to see what your real user experienced while navigating your site or application. You can also view search results in a map or pivot chart. For more information, see Replaying sessions, hits, and sequences and Visualizing search results.
You can perform the following tasks from the Search dashboards:
•
Searching and investigating hits
•
Searching and investigating sessions
•
Searching and investigating sequences
•
Viewing search results in a map
•
Viewing search results in pivot charts
•
Replaying sessions, hits, and sequences
•
Repeating the last search
•
Saving searches
•
Running saved searches
•
Clearing search results

Searching and investigating hits

You can search for hits by time range, hit detail, analyzer, content category, or some combination of these parameters. You can also define match conditions to create very specific searches.
In the Search Hits dashboard, you can run a simple search or an expert search to find hits. You can also rerun the last search, save a search, load and run a saved search, or clear search results.
For more information, see the following topics:
•
Defining simple searches for hits
•
Defining expert searches for hits
•
Understanding search hits results
•
Investigating hit results
•
Viewing search results in a map
•
Viewing search results in pivot charts
•
Replaying sessions, hits, and sequences
•
Repeating the last search
•
Saving searches
•
Running saved searches
•
Clearing search results
•
Defining match conditions for expert searches
Documentos relacionados

The document was helpful.

Seleccionar calificación

I easily found the information I needed.

Seleccionar calificación