Chatta subito con l'assistenza
Chat con il supporto

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

Defining custom field updates

When adding or editing custom field updates, you can set the following options.
 
Table 64. Defining custom field updates
Option
Setting the Option
Custom Field
Select a custom field or click New to create a custom field. For more information, see Creating new custom fields.
Source
Select the type of update, such as Fixed Value, Script Output, Session Custom Field, or one of the available details.
NOTE: The other fields displayed in this pane depend on this selection.
Source Detail
If the Source you selected requires additional detail, specify the detail in this box. For example, if you selected Primary Value=Fixed Value, type the amount by which you want to increment/decrement the custom field.
Extraction Expression
Optional—if available, you can create an extraction expression. For more information, see Defining extraction expressions.
Update If Blank
Optional—override the setting defined for the custom field. Select to allow the custom field to be set to an empty (blank) value. Clear (default) to ignore blank values, that is, an existing value is not replaced by a new value if the new value is blank.
Value Assignment
Optional—override the setting defined for the custom field. Select an option that reflects how you want to handle values for the custom field. For more information, see Value assignment mode option.
Separator
Optional—override the setting defined for the custom field. When the Value Assignment Mode is set to one of the Append options, you can define a separator to be inserted between values. Typical separators are a comma or a colon, but you can use any character or combination of characters that suits your needs.
Update
Select the update criteria. See Update criteria option.
Update criteria option
The following table describes the possible values for the Update Criteria option, where <status> can be OK, Error, Warning, or a combination thereof.
 
Table 65. Update criteria option
Analyzer
Always (default)
Other Options
Hit
Updates custom fields if a hit satisfies the match conditions.
You can choose to update based on:
•
final hit status = <status>
•
hit analyzer status = <status>
Sequence
Commits pending custom field updates if the sequence stops.
You can commit pending updates based on:
•
sequence analyzer status = <status>
Session
Updates custom fields if a session satisfies the match conditions.
You can choose to update based on:
•
final session status = <status>
•
session analyzer status = <status>

Executing scripts

Scripts are snippets of custom logic written in the Groovy scripting language. You can create scripts to extend the functionality of Foglight APM Appliances. For more information, see Managing scripts.
 
* 
NOTE: Scripts for traffic analysis run on the Archiver database and directly affect data analysis and storage activities. Foglight also offers a Script Console dashboard. You can use the Script Console to query data stored in topology objects in the Foglight database.
Any type of analyzer (or special event) can execute a script. Analyzers can use the output variables published by the script to update custom fields or metrics.
Figure 86. Scripts view
You can add, edit, and remove scripts from an analyzer using the standard controls. For more information, see the following topics:
•
Executing scripts
•
Creating new scripts

Executing scripts

To execute a script from an analyzer, you specify the name of a validated script and the execution criteria. By default, analyzers execute scripts whenever the analyzer’s conditions are satisfied. For hit and session analyzers, you can choose a different criteria for executing scripts.
The following table describes the behavior of the Executing Criteria options, where <status> can be OK, Error, Warning, or a combination thereof.
 
Table 66. Executing scripts
Analyzer
Always (default)
Other Options
Hit
Executes scripts if a hit satisfies the match conditions.
You can choose to execute scripts based on:
•
final hit status = <status> OR
•
hit analyzer status = <status>
Sequence
Executes scripts if the event conditions are satisfied.
Not applicable.
Session
Executes scripts if a session satisfies the match conditions.
You can choose to execute scripts based on:
•
final session status = <status> OR
•
session analyzer status = <status>

Creating new scripts

If an existing script does not suit your purposes, you can create a new script on the fly. You create the script in exactly the same way you would if you selected Scripts from the Advanced Options. For more information, see Managing scripts and Creating new scripts on the fly.
Scripts are global objects. If you create a new script while defining your analyzer’s actions, the script is available to all analyzers that can execute the same type of script. For more information on types of script, see Select an appropriate API.
Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione