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

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

Creating custom metrics

Custom metrics are user-defined, numeric variables. If an existing metric does not satisfy your requirements, you can create a custom metric. For example, a typical reason to create a custom metric is to count some kind of error. For more information, see Defining custom metrics.
You do not set explicit values for custom metrics, instead you use analyzers to increment or decrement the value. An analyzer can update custom metrics using any of the following values:
•
Fixed values—For example, counter-type metrics are usually incremented by 1.
•
Script outputs—Analyzers can update metrics using values that are generated by Groovy scripts and exposed as output variables. The script is executed as needed to determine the metric increment value.
•
Session custom fields—Analyzers can update metrics using numeric data from a session custom field.
•
Hit details (numeric)—Analyzers can update metrics using any numeric data associated with a hit. For example, you can update a metric with Request Field values or Cookie values.
Updating custom metric values
For custom metrics, you can define when the metrics are updated. By default, analyzers update the metrics when the analyzer match conditions are satisfied or, in the case of sequence events, when the sequence stops. You can update a custom metric on a different schedule by changing its Increment policy. The following table describes the behavior of the Increment options, where <status> can be OK, Error, Warning, or a combination thereof.
 
Table 60. Updating custom metric values
Analyzer
Always Update (default)
Other Options
Hit
If the hit satisfies the match conditions, the custom metric is updated immediately.
You can update a custom metric based on the status of the analyzer or hit:
•
final hit status = <status>
•
hit analyzer status = <status>
Sequence
At the end of the sequence, if the sequence satisfies the event’s match conditions, the analyzer-scoped custom metric is updated.
You can update an analyzer-scoped custom metric based on the <status> of the analyzer.
Sequence Event
At the end of a sequence, if the sequence satisfies the event’s match conditions, the event-scoped custom metric is updated.
You can update an event-scoped custom metric based on the <status> of the analyzer.
Session
At the end of a session, if the session satisfies the match conditions, the custom metric is updated.
You can update a custom metric based on the status of the analyzer or session:
•
final session status = <status>
•
session analyzer status = <status>
Defining custom metrics
When adding or editing custom metrics, you can set the following options.
 
Table 61. Defining custom metrics
Option
Setting the Option
Name
Specify a unique name for the custom metric.
Description
Optional—summarize the purpose of this custom metric.
Source
Select the source of the value used to increment this metric—such as Fixed Value, Script Output, Session Custom Field, or one of the available details.
NOTE: The other available fields change depending on the selected Source.
Source Detail
If the Source you selected requires additional detail, specify the detail in this box. For example, if you selected Fixed Value, type the amount by which you want to increment/decrement the metric.
Extraction Expression
Optional—if available, you can create a user-defined expression that extracts a portion of the source’s value. For example, if your source contained “$99,” you can extract “99” as your increment value. For more information, see Defining extraction expressions.
Increment
By default, a custom metric is always incremented. You can change the update policy. For more information, see Updating custom metric values.
For an example, see Adding custom metrics.

Changing the name of metric topology objects

By default, Foglight stores all metrics in a topology object with the same name as the analyzer. You can change the name of the topology object. You can also break out the metrics into multiple, dynamically-named topology objects using a name substitution token.
Renaming a topology object
You may want to rename a topology object if you have multiple analyzers with similar names. You can make your topology objects easier to locate by adding your name to the object name or by including some other identifying text. To rename a topology object, select Customize Name and type the new name in the associated field.
Creating dynamically-named topology objects
Foglight automatically creates topology objects to track hits that return HTTP error codes. However, you could achieve the same result using dynamically-named topology objects. In this example, an analyzer matches hits when the Response Code is 400 or greater than 401. By using Topology Object Naming, this one analyzer can create objects for each error code and collect data separately.
In the Metrics view, in the Topology Object Naming pane, this analyzer has a customized name that includes the $1 token. The $1 token is defined as a Response Code, which contains the error code.
Figure 80. Edit Hit Analyzer view
As this analyzer matches hits in the monitored traffic, new topology objects are created dynamically for each error code encountered in the hits. For example,
•
HTTP Error Code 400
•
HTTP Error Code 403
•
HTTP Error Code 404
•
and so on
The topology objects created by this default analyzer appear in the Data dashboard. In the navigation panel, under Dashboards, navigate to Configuration > Data. Expand APM > Transactions.
Figure 81. Configuration > Data > APM > Transactions view
When you select a topology object, you can see its list of properties and the Property Viewer opens to the right of the list, as shown in the following image. The standard and custom metrics are organized under Measurements. Under Pivots, you can find standard and custom metrics by pivot category.
Figure 82. Pivots category
For instructions, see Breaking out metrics into dynamically-named topology objects.

Understanding pivots for analyzer metrics

With pivots, you can collect additional data based on a category, such as Country. Each item in a category generates a new set of metrics (standard metrics plus custom metrics) and associated data. If you have dynamically-named topology objects, each object includes the pivots. For a list of pivot categories, see Understanding pivot categories.
 
* 
IMPORTANT: Foglight APM contributes only a portion of all data handled by Foglight. To avoid flooding Foglight with unnecessary data, avoid selecting all pivot categories for analyzers that fire frequently. As a rule of thumb, collect just the data you need.
For example, if you select Country as a pivot category for logins, and people from two different countries visit your site, you get a total of three sets of metrics, the basic set and one for each country.
Example of pivots for analyzer metrics
To select pivots for an analyzer, click Pivots and select the pivot categories. For detailed instructions, see Selecting pivot categories.
 
* 
IMPORTANT: The analyzer-level pivot categories inherit settings from the Traffic Analysis > Pivots dashboard. Although you may be able to select a pivot category for an analyzer, if that pivot category does not have any values defined on the Traffic Analysis > Pivots > Pivot Objects dashboard, the analyzer cannot generate the pivot metrics. For more information, see Managing pivots.
Example: Investigating a problem report using pivots
You have a hit analyzer, called Login, that tracks when end users access their web site login page. Standard metrics only are collected—no pivot categories, no custom metrics.
An end user reports having difficulties accessing the login page using BrowserA version 1.1, but has no problem using BrowserB. In Foglight, you update the Login hit analyzer to gather more data. Because you do not know if any other browsers or browser versions are also affected, you enable the Browser category as a pivot. From the resulting data, you can see when and where the errors occur. You may discover that the problem affects only a few versions of BrowserA, and you can focus your efforts to resolve the problem on those browsers.

Publishing hit metrics for use in the Geographical Perspective dashboard

Foglight users with the role of APM Operator use the Geographical Perspective dashboard to understand how monitored web sites and web applications are performing by country, region, and/or city. As the APM Administrator, you control which metrics are available to the Geographical Perspective dashboard by enabling map-based metric snapshots on an analyzer-by-analyzer basis. You choose the level of geographical detail you want to display on the Geographical Perspective dashboard—that is, data points by country, region, and/or city—and decide how many data points to plot at each level, from 0 to 100. For example, you could enable the top 10 countries and the top 100 cities. For detailed instructions, see Publishing metric timeslices for the Geographical Perspectives dashboard.
Figure 83. Maps dialog box
While the hit analyzer is active, it publishes snapshots of its metric data every five minutes. In the Geographical Perspective dashboard, you select a measurement (metric) and a five-minute timeslice, and the dashboard displays metric data from the appropriate snapshot. For more information, navigate to APM > Geographical Perspective, select the Help tab, and click More.
関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択