Foglight APM for Real User Experience 5.9.9

Table 10. Simple hit search criteria
occurred within the	Select the time range for the search. If no other options are set, the search returns all hits occurring within the specified time range. TIP: An APM Administrator can increase or decrease the maximum time range displayed in the list through the Configure Advanced Options > Settings dashboard. See the Search Time Range Limit option under the Archiver Query Settings.
Hit Analyzer	Optional—search by hit analyzer name. Specify the name of the hit analyzer that captures the data you want to find.
Request Path	Optional—search hits based on the URI path. Specify a full or partial path using asterisks () as wildcards as required. For example, /css returns all hits that have the subdirectory css in the Request Path hit detail.
Content Category	Optional—search for hits in a particular content category. Select a content category from the list.
Violates the	Optional—search for hits that caused a specified threshold to be exceeded. Select a threshold from the list.

Click Search.

The Search Hits table contains the results of the search.

Defining expert searches for hits

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.

To define and run an expert hit search:

In the navigation panel, under Dashboards, click APM > Search > Hits.

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.

Specify the search criteria.

Table 11. Expert hit search criteria
Time Range	Select the time range for the search. If no other options are set, the search returns all hits occurring within the specified time range. TIP: An APM Administrator can increase or decrease the maximum time range displayed in the list through the Configure Advanced Options > Settings dashboard. See the Search Time Range Limit option under the Archiver Query Settings.
starting	If you selected Time Range=specified time range, click the Calendar icon and specify a date and time.
ending	If you selected Time Range=specified time range, select a length of time to search (starting from the starting time).
Hit Analyzer	Optional—search by hit analyzer name. Specify the name of the hit analyzer that captures the data you want to find.
Response Content	Optional—search by keyword. Specify a keyword that you want to match in the Response Content hit detail.
Request Path	Optional—search hits based on the URI path. Specify a full or partial path using asterisks () as wildcards as required. For example, /css returns all hits that have the subdirectory css in the Request Path hit detail.
Content Category	Optional—search for hits in a particular content category. Select a content category from the list.
Match Conditions	Optional—specify one or more conditions to match. Click Add. You can define a match condition on any hit detail or metric listed in the Source list. For help creating match conditions, see Defining match conditions for expert searches.

Click Search.

The Search Hits table contains the results of the search.

Understanding search hits results

When the search ends, the results are displayed in the Search Hits table. The search parameters appear above the table. If no hits matched the search parameters, the table is empty.


	TIP: By default, a hit search returns a maximum of 1,000 hits. An APM Administrator can change this limit using the Hit Search Result Limit setting in the Configure Advanced Options > Settings dashboard. The APM Administrator can increase or decrease this limit within the range of 1 to 1,000 hits, but can never increase it over 1,000 hits.

Figure 24. Search Hits dashboard

The Search Hits table may contain some or all of the following columns. To hide/show columns, click the Customizer

icon (beside the Search field) and select the columns to show.

Table 12. Search Hits table

Column

Description

Sessions

When a hit belongs to a session, the Session Explorer

and Session Detail View

icons appear in this column. You can drill down to session details by clicking one of these icons.

Status

Indicates the hit status using the standard severity icons:

•

•

•

•

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:

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 25. 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.

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.

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 26. Hit Preview