立即与支持人员聊天
与支持团队交流

Foglight APM for Real User Experience 5.9.11 - 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 hit results

This workflow walks through how to use the data in the Search Hits table and how to drill down to more details about a specific hit or the session to which it belongs. Your own investigative workflow will depend on the problems you are trying to resolve.

 
* 
NOTE: Typically you want to design searches that limit the search results in a meaningful way, such as finding all hits that triggered a hit analyzer or all hits with an end-to-end time greater than 10 seconds. A restrictive search makes your investigation work much easier.
To review hit search results:
1
From the Search Hits dashboard, run a search.
•
Running saved searches
•
Repeating the last search
•
Defining simple searches for hits
•
Defining expert searches for hits
For this walkthrough, we created a simple search with Content Category = HTML, and then sorted by Back-End Time (ms).
Figure 27. Search Hits dashboard (Content Category = HTML)
When a hit belongs to a session, the Session Explorer and Session Detail View icons appear in the Sessions column. You can view the selected hit within the context of a session and assess the other hits that occurred within the session. For more information about using these views, see Investigating issues.
2
Choose an interesting HTML hit to investigate.
For example, choose a hit that displays one or more of the following characteristics:
•
Status—look for icons other than the Normal icon. A hit can be set to a non-normal status due to a client or browser error code or when the hit matched some set of conditions defined within a hit analyzer. APM Administrators define and manage hit analyzers.
•
Code—look for client error codes (400+) or server error codes (500+). Remember though that Web 2.0 applications may not return error codes, because they redirect users to a helpful error page rather than a generic error page. In this case, you need to rely on analyzers catching the errors and setting the hit status to non-normal.
•
End-to-End Time—very high end-to-end times may indicate a problem with the amount of content on a page or a very slow web server.
•
Back End Time—very high back end times may indicate a problem with the web server.
•
Exception—any exceptions should be reported to the application developer.
3
To display the contents of the hit, click Replay in the Hits column.
If the hit is an HTML page, you see an approximation of the page as viewed by the user. If you select an image, the Replay window shows the image. If you select a text file such as a CSS file or a JavaScript file, the browser attempts to download the file. In some cases, content may be missing. For more information, see Understanding what happens when content is unavailable.
Figure 28. Hit Preview
4
To drill down to the hit details, click Hit Detail View in the Hits column. You can open the view in the current browser window or a new window.
The Hit Detail View opens, displaying details and performance metrics for the hit. As you review the details, you may want to collapse the views you are not interested in. Then you can focus on the details of interest. Click the Client Detail, Metric Updates, and Other Information links to view additional information about the hit.
Figure 29. Hit Details View
5
If you notice something in the hit details or metrics that looks interesting, you may want to view all the hits by this detail to see if a pattern emerges.
For example, you may suspect that a slow End-to-End Time is typical for the user’s region or service provider. To test your hypothesis, you can create a pivot chart for End-to-End Time by Region or ISP. To create a pivot chart, return to the search results. Click Pivot . For more information, see Viewing search results in pivot charts.
6
To map your results geographically, return to the search results. Click Map . For more information, see Viewing search results in a map.

Searching and investigating sessions

You can search for sessions by time range, session identifier, user name, the status of sessions (active or ended), or some combination of these parameters. You can also define match conditions to create very specific searches.

In the Search Sessions dashboard, you can run a simple search or an expert search to find sessions. 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 sessions
•
Defining expert searches for sessions
•
Understanding search sessions results
•
Investigating issues reported during real user sessions
•
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 simple searches for sessions

A simple search enables you to search for sessions using the most frequently-used search criteria. If you want to search for sessions that occurred within a particular time range or hits that match some set of conditions, you need to define an expert search instead.

To define and run a simple session search:
1
In the navigation panel, under Dashboards, click APM > Search > Sessions.
2
Click Simple Search.
3
Specify the search criteria.
 
Table 13. Simple session search criteria
Find sessions that...

In the first list, select the start condition for the search. In the second list, select the time range for the search. If no other options are set, the search returns all sessions occurring within the specified time range.

TIP: An APM Administrator can increase or decrease the maximum time range displayed in the time range list through the Configure Advanced Options > Settings dashboard. See the Search Time Range Limit option under the Archiver Query Settings.
are currently

Optional—specify whether you want active or ended sessions. Select this check box and select the state from the list.

Session ID

Optional—search for a session by session identifier. Specify the session identifier you that you want to match.

Username

Optional—search for a real user by user name. Specify the user name (case-insensitive) that you want to match.

Session Hit Count Matching Hit Analyzer

Optional—search for hits that triggered the specified hit analyzer during the session.

Figure 30. Simple Search (sessions) dialog box
4
Click Search.
The Search Sessions table contains the results of the search.
Related Topics
•
Defining expert searches for sessions
•
Understanding search sessions results
•
Investigating issues

Defining expert searches for sessions

You can run a search using the same options as a simple search. You can also define a time range or some set of conditions, such as session with a specified duration.

 
* 
NOTE: The Archiver stores session duration in milliseconds, but the UI displays it in seconds. Therefore, if you search sessions based on duration, you may see results that appear to fall outside the search criteria. For example, defining a match condition with “Session Duration > 10” may return search results that appear to match “Session Duration >= 10”. In this case, a session that appears to be equal to 10 seconds actually has a duration greater than 10 seconds, such as 10.4322 seconds, but the UI does not display the decimal places.
To define and run an expert session search:
1
In the navigation panel, under Dashboards, click APM > Search > Session.
2
Click Expert Search.
If you defined a simple search before switching to an expert search, the Expert Search dialog box displays the same values for the options you selected in the Simple Search dialog box.
3
Specify the search criteria.
 
Table 14. Expert session search criteria
Find sessions that...

In the first list, select the start condition for the search. In the second list, select the time range for the search. If no other options are set, the search returns all sessions occurring within the specified time range.

TIP: An APM Administrator can increase or decrease the maximum time range displayed in the time range list through the Configure Advanced Options > Settings dashboard. See the Search Time Range Limit option under the Archiver Query Settings.
are currently

Optional—specify whether you want active or completed sessions. Select this check box and select the state from the list.

Session ID

Optional—search for a session by session identifier. Specify the session identifier you that you want to match.

Username

Optional—search for a real user by user name. Specify the user name (case-insensitive) that you want to match.

Match Conditions

Optional—specify one or more conditions to match. Click Add. You can define a condition based on any detail or metric listed in the Source list. For help creating match conditions, see Defining match conditions for expert searches.

Figure 31. Expert Search (sessions) dialog box
4
Click Search.
The Search Sessions table contains the results of the search.
5
Next Steps: See Investigating issues.
Related Topics
•
Defining simple searches for sessions
•
Understanding search sessions results
•
Investigating issues
相关文档

The document was helpful.

选择评级

I easily found the information I needed.

选择评级