Chat now with support
Chat mit Support

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

Building a pattern that matches multiple characters

Using regular expressions you can define a pattern to match a multi-character pattern. For example, you can write a regular expression to match all hosts whose names contain Host and are followed by exactly two digits. That means you want to match the following strings:
•
Host01
•
Host03
But not:
•
Host01-bckp
The expression that matches this pattern is: Host[0-9][0-9].
 
* 
TIP: Because there is no trailing .* in the expression, the host name with the -bckp suffix does not match.
Going further, you can write an expression that matches all hosts whose names contain Host, followed by exactly two digits, and optionally a lowercase letter. That means you want to match the following strings:
•
Host01
•
Host03a
But still not:
•
Host01-bckp
The expression that matches this pattern is: Host[0-9][0-9][a-z]?.
 
* 
NOTE: The question mark ‘?’ in regular expressions is also a quantifier, and not a single character wild character like in some file systems.

Using advanced quantifiers

In addition to asterisk ‘*’ and question mark ‘?’, there are additional quantifiers that are supported in regular expressions:
•
The plus sign ‘+’ means one or more times. For example, case[0-9]+ matches case1, case12345, but not simply case.
•
The braces “{}” express a range. For example:
•
{3} occur exactly three times.
•
{2,4} occur at least two times and as many as four times.
•
{3,} occur at least three times up to infinity.
You can use this notation instead of the common quantifiers:
•
An asterisk ‘*’ has the same meaning as {0,}.
•
A plus sign ‘+’ has the same meaning as {1,}.
•
A question mark ‘?’ has the same meaning as {0,1}.

Using special characters and regular expression flags

Special characters in regular expressions the regular expressions further extend their flexibility in advanced use cases.
•
The caret ‘^’ reverses the meaning of a regular expression element. For example, [^KLM] matches a single character that is not K, L, or M.
In the Windows® drive mapping example, the following expression excludes all drives except K, L, or M:
(?x)[^KLM]:.* # Exclude all drives except K thru M
•
The backslash ‘\’ is an escape character. It indicates that the next character is a special character and interpreted literally.
•
A backslash ‘\’ followed by a lowercase ‘d’, \d, means a digit.
•
A backslash ‘\’ followed by a lowercase ‘w’, \w, means a word character (an alphanumeric character or an underscore ‘_’). It has the same meaning as [a-zA-Z_0-9].
•
A backslash ‘\’ followed by a lowercase ‘s’, \s, means a white space character. It has the same meaning as [\t\n\x0b\r\f].
•
Two backslashes “\\” followed by a period ‘.’, \\., means a literal dot.
•
The flag (?i) makes the regular expression case insensitive. In the Foglight APM, the Add OS Monitor wizard uses this flag in the Resource Mapping regular expression. For example: (?i).*host.*.
•
The flag (?x) allows you to add comments to explain a complex or unusual pattern. The comment starts with a number sign ‘#’. For example: (?x)[KLM]:.* # We dislike drives K through M.

Grouping elements in a pattern

The regular expression syntax provides a way to group elements together and use groups together with other operators, as required.
•
Use parentheses “()” to group elements together.
•
For example, to match a period ‘.’ followed by one or more alphabetic characters, write (\\.[A-Za-z]+).
•
Use a common quantifier with a group.
•
For example, to match the above group ((\\.[A-Za-z]+)) zero or more times, write (\\.[A-Za-z]+)*.
•
Use a pipe ‘|’ with a set of alternatives.
•
For example, to use a prefix that is either dev or prod, write (dev|prod).
Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen