サポートと今すぐチャット
サポートとのチャット

Foglight APM for Real User Experience 5.9.9 - Administration and Configuration Guide

Getting started Configuring traffic capture
Managing Sniffers Managing Archivers Managing capture groups Managing sessionizing policies Managing monitored ports Managing monitored IP addresses Managing monitored subnets Managing identifiers for virtual addressing schemes Managing private keys Managing web services and SOAP operations
Configuring traffic analysis Configuring analyzers Capturing traffic outside the network Configuring advanced options Integrating Foglight APM with other products Maintaining and troubleshooting Appendix: Building regular expressions in Foglight Appendix: Traffic analysis processing
Understanding the traffic analysis workflow Stage 1: Run hit analysis Stage 2: Run sequence analysis Stage 3: Finalize stopped sequences Stage 4: Finalize the session Example of interdependent analyzers Online-Only Topics
Removing items from a table Defining extraction expressions Adding, copying, and editing archivers Testing archivers Configuring archiver database shard settings Adding, copying, and editing sniffers Testing sniffers Adding and editing capture groups Testing capture groups Adding and copying sessionizing policies Editing sessionizing policies Selecting session identifiers from a discovery list Adding and editing session identifier variables Organizing session identifiers Selecting user name variables from a discovery list Adding and editing username rules Selecting URL prefixes from a discovery list Adding or adding URL prefixes Selecting ports from a discovery list Adding or editing monitored ports Selecting IP addresses from a discovery list Adding or editing monitored IP addresses Looking up host names for all monitored IP addresses Associating private keys with IP addresses Selecting subnets from a discovery list Adding and editing monitored subnets Adding identifiers Editing identifiers Finding IP addresses in HTTP headers Configuring a custom HTTP header using Microsoft IIS Manager Adding and editing local private keys Adding and editing HSM private keys Exporting keys using Microsoft Management Console Adding or editing web services Importing WSDL files to define web services Managing custom fields and metrics Adding, copying, and editing custom fields Removing custom fields Editing custom metrics Removing custom metrics Managing sensitive data Adding, copying, and editing sensitive hit detail policies Adding, copying, and editing sensitive content expression policies Modifying members of pivot categories Selecting aliases from a discovery list Adding, copying, and editing domain rules Adding, copying, and editing large hit details Adding, copying, and editing URL classifiers Reviewing rules for browser category, browser, and operating system hit details Adding user-defined user agent rules Adding and editing additional parsed response types Adding and editing captured request body types Adding, copying, and editing scripts Removing scripts Referencing configuration objects in a script Testing regular expressions Syntax for test data Adding simple hit analyzers using the Setup Wizard Adding simple sequence analyzers using the Setup Wizard Adding analyzers Copying analyzers Editing analyzers Adding and editing conditions Creating a simple Boolean expression Creating a complex Boolean expression Disabling standard metrics generated by a hit analyzer Adding custom metrics Editing custom metrics Selecting pivot categories Breaking out metrics into dynamically-named topology objects Publishing metric timeslices for the Geographical Perspectives dashboard Changing SLA thresholds Adding custom field updates Editing custom field updates Adding scripts to an analyzer Editing scripts Creating new scripts on the fly Adding hit storage restrictions Editing hit storage restrictions Adding sequence events Editing sequence events Adding static page elements Editing static page elements Viewing resource files defined by static page elements Adding and editing subnet filters Exporting configurations Exporting encrypted configurations Restoring a previous configuration Importing saved configurations Importing hit analysis configurations from Foglight Experience Viewer Using the Import Configuration Wizard

Reviewing default hit analyzers

This high-level workflow introduces you to hit analyzers by reviewing two default hit analyzers. You may want to try these steps in Foglight.
1
On the navigation panel, under Dashboards, click APM > Configure > Traffic Analysis.
2
In the Traffic Analysis dashboard, expand Hit Analyzers.
You can add, copy, edit, and remove hit analyzers using the standard controls. You can also click Setup Wizard to be guided through the process of creating a simple hit analyzer that matches on the request path.
From the Enabled column, you can see that some of the default analyzers are enabled, which means the Archiver evaluates their match conditions for captured hits. The disabled analyzers are ignored. In the Phase column, you can see that each hit analyzer runs in one of three possible phases: Filtering, Main, and Final (not show n).
For this walkthrough, we examine two analyzers, one that runs in the Filtering phase and one that runs in the Main phase.
3
In the row containing the filter Default Type Exclusions, click Edit .
The Edit Hit Analyzer dashboard appears.
4
Expand the Match Conditions view.
First, we notice that this analyzer has multiple conditions, one per row. At the bottom left, you can see that the Grouping for the conditions is a Boolean OR, so only one condition needs to be matched to trigger this analyzer. For more information, see Configuring conditions.
These conditions match hits that would inflate the total hit count for a page, such as the hits required to get the images for the page. If we enable this analyzer, all hits on the web server that retrieve applications, images, CSS files, and JavaScript are excluded from data processing and storage. For example, a hit to retrieve an image does not increment a hit count metric. In some environments, this can be useful for keeping metrics meaningful.
A hit analyzer that runs in the Filtering phase has one implicit action, which is to drop any hits that match the conditions. This means that the Sniffer does not process the hit and the hit is not sent it to the Archiver. If you want to keep a hit and specify actions to perform on it, you need to specify a hit analyzer that runs in the Main or Final phase. We look at a Main phase hit analyzer in the next steps.
 
* 
TIP: You should consider using Filtering phase hit analyzers to reduce data processing and storage for hits you are not interested in.
5
At the bottom of the dashboard, click Cancel to return to the Traffic Analysis dashboard.
Now let’s take a look at a Main phase hit analyzer. Most of the analyzers you create run in the Main phase. This analyzer marks the first and last HTML pages viewed by a user during the user’s session.
6
In the row containing the filter Default Session Page Visit Custom Fields, click Edit .
The Edit Hit Analyzer dashboard appears.
7
Expand the Match Conditions view.
This analyzer is triggered for hits on HTML pages. Below the match conditions, we can see a set of views that represent actions that happen when a hit matches the condition. Some of the headings are displayed in bold text, in this case, Metrics, Custom Fields, and Options. The bold text indicates that the option has been defined or modified from its default behavior. For this workflow, we review all the bolded views.
8
Expand Metrics.
Notice that Generate Standard Metrics is deselected, which represents a change from the default behavior for hit analyzers.
Metrics, and the ability to generate and update them in flexible ways, is a key concept in Foglight APM. In some cases, like this one where the analyzer only annotates data, we do not need these metrics. In most cases, you use analyzers to match interesting hits, and so you want to collect more data about them. Standard metrics are a predefined set of metrics that includes metrics such as hit count and page end-to-end time. You can set service-level thresholds for the metrics, generate metrics by pivot category (resulting in metrics such as page end-to-end time by browser), and make metrics available to the top-level Geographic Perspective dashboard. You can also create custom metrics. For more information, see Working with metrics.
9
Expand Custom Fields.
This hit analyzer uses default, session-scoped custom fields to annotate the hit that starts a session and the hit that ends a session. You can view the scope for a custom field by clicking Edit or you can see the scope for all custom fields in the Custom Fields view on the Traffic Analysis dashboard. The Entry Page is set on the first hit for a user session. Once it is set for the current session, it is not reset. The Last Page Visited field is reset for every hit in a session. At the end of the session, this field contains the last page viewed before the session ended.
10
Expand Options.
These options support searches based on an analyzer’s name. In this case, we are not interested in searching by analyzer name, so Mark Hits is set to Never.
Marking a hit annotates the hit with the analyzer name. Searchable includes the analyzer name in the Expert Search dialog box. For more information, see Setting searchability options for analyzers.
11
This completes the walkthrough. Click Cancel to avoid changing the default analyzer.

Tips for creating effective hit analyzers

Keep in mind these tips for creating effective match conditions for hit analyzers:
•
Make the match conditions as specific as possible.
•
Avoid creating hit analyzers that match every hit, unless you truly want to perform an action on every hit.
•
Whenever a hit analyzer (Foo) needs the value of a custom field that is set by another hit analyzer (Bar) for the same hit, ensure that Bar runs in the Main phase and Foo runs in the Final phase. You cannot control the order in which analyzers within the same phase execute.
•
Minimize the use of regular expressions in match conditions (especially with large hit details such as Request Content or Response Content). Regular expression processing can negatively affect performance when run on every hit.
•
Avoid using the Script Output option in match conditions. Executing a script on every hit can negatively affect performance.
•
When creating multiple conditions, if a condition uses regular expressions or scripting you should add it as the last condition. This allows simpler conditions to be evaluated first.

Configuring hit analyzers

When adding, copying, or editing a hit analyzer, you can define the following options.
 
* 
NOTE: When editing a hit analyzer, click Properties to edit the Name, Description, and the Enabled options.
 
Table 53. Configuring hit analyzers
Option
Setting the Option
Name
Specify a unique name.
Description
Optional—summarize the reason you created the hit analyzer, including the actions it performs.
Enabled
Select this option to activate the analyzer as soon as you finish defining it.
Match Conditions
Add conditions that need to be met before the analyzer’s actions run. Using match conditions, you can target the actions of an analyzer to specific types of web traffic. For more information, see Configuring conditions.
Metrics
By default, the analyzer creates standard metrics for the hit. You can change the default behavior, add custom metrics, change how topology objects are created and named, define pivots, define SLA thresholds, and publish data for use in maps. For more information, see Working with metrics.
Custom Fields
Optional—update the values of custom fields. For more information, see Updating custom fields.
Scripts
Optional—execute a script. For more information, see Executing scripts.
Error Conditions
Optional—add conditions that need to be met before changing the status of the hit to Error. For more information, see Defining error and warning conditions.
Warning Conditions
Optional—add conditions that need to be met before changing the status of the hit to Warning. For more information, see Defining error and warning conditions.
Hit Storage Restrictions
By default, the Archiver stores all hits, regardless of the hit analyzer status. To change this behavior, see Defining hit storage restrictions for hit analyzers.
Options
By default, hits that satisfy an analyzer’s match conditions are annotated with the analyzer’s name to support searching by analyzer. To change this behavior, see Setting searchability options for analyzers.

Introducing sequence analyzers

A sequence is a series of hits or a set of transactions executed by an end user during their visit to a web site or while using a web application. Any given user session may contain multiple sequences. You can capture information about sequences by defining sequence analyzers.
A sequence analyzer identifies distinct sequences during active user sessions. You define sequence analyzers by creating a set of sequence events, which usually includes a start sequence event, some intermediate events, and a stop sequence event. Each event is evaluated independently. When an event’s conditions are satisfied, the analyzer runs the actions defined for the event. For more information, see Defining events for sequence analyzers.
 
* 
NOTE: A key distinction between hit analyzers and sequence analyzers is that hit analyzers examine the hit currently being processed, while sequence analyzers act on a series of hits within the active session.
Sequence analyzers are most commonly used to identify a logical sequence, such as the set of hits associated with how a customer uses a shopping cart on a web site or the set of hits generated by an employee navigating a critical workflow in your intranet application. However, you can also use sequence analyzers to detect and alert on any activity within a session. For example, you can use a sequence analyzer to detect multiple events that provide information about site problems and client activity within a related set of pages.
For more information, see the following topics:
•
Configuring sequence analyzers
関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択