User experience management measure-specific attributes
Business Transaction/Evaluation/Filter/Splitting Values
- Match: Select an operator from the list to indicate the type of matching and select or clear the Case Sensitive and Ignore Whitespaces to further define the match.
- Value: The value to match.
- Evaluation: Select the method used to evaluate the transformation regex from the list.
- Transformation Regex (optional): Enter a transformation regular expression to extract relevant information. The resulting value is the tagged expression or, if more expressions are present, the combination of all tagged expressions separated with a blank.
For example, a regex ID of(.\*)
and an input ofID=66
result in a value of66
. Also, a regex ID of([^_]*)_[^_]*_(.*)
and an input ofID=66_867_07
results in a value of66 07
.
- Key for ADK String Value: Select an operator from the list to indicate how to match the string value from the JavaScript ADK, then enter the string value.
- Transformation Regex (optional): Enter a transformation regular expression to extract relevant information. The resulting value is the tagged expression or, if more expressions are present, the combination of all tagged expressions separated with a blank.
For example, a regex ID of(.\*)
and an input ofID=66
result in a value of66
. Also, a regex ID of([^_]*)_[^_]*_(.*)
and an input ofID=66_867_07
results in a value of66 07
.
- Splitting URI Pattern: Select a pattern from the list to indicate how to match the URI for splitting. The pattern displays in the Transformational Regex field. You can select Custom from the list and define your own URI pattern.
- Transformation Regex (optional): Enter a transformation regular expression to extract relevant information. The resulting value is the tagged expression or, if more expressions are present, the combination of all tagged expressions separated with a blank.
For example, a regex ID of(.\*)
and an input ofID=66
result in a value of66
. Also, a regex ID of([^_]*)_[^_]*_(.*)
and an input ofID=66_867_07
results in a value of66 07
.
- Transformation Regex (optional): Enter a transformation regular expression to extract relevant information. The resulting value is the tagged expression or, if more expressions are present, the combination of all tagged expressions separated with a blank.
For example, a regex ID of(.\*)
and an input ofID=66
result in a value of66
. Also, a regex ID of([^_]*)_[^_]*_(.*)
and an input ofID=66_867_07
results in a value of66 07
.
- Custom Value Name:
- Transformation Regex (optional): Enter a transformation regular expression to extract relevant information. The resulting value is the tagged expression or, if more expressions are present, the combination of all tagged expressions separated with a blank.
For example, a regex ID of(.\*)
and an input ofID=66
result in a value of66
. Also, a regex ID of([^_]*)_[^_]*_(.*)
and an input ofID=66_867_07
results in a value of66 07
.
These measures are typically used for business transactions. They let you name a domain where CDN or third party content is loaded from that has the largest impact on page load time. Use the selector in the Only count domain provider with busy time higher than field to set the time (in milliseconds).
This measure collects metadata captured on a user action.
- Metadata ID: Specify an ID of a configured Metadata item. See the User Experience settings in a given System Profile.
- Transformation Regex (optional): Enter a transformation regular expression to extract relevant information. The resulting value is the tagged expression or, if more expressions are present, the combination of all tagged expressions separated with a blank.
For example, a regex ID of(.\*)
and an input ofID=66
result in a value of66
. Also, a regex ID of([^_]*)_[^_]*_(.*)
and an input ofID=66_867_07
results in a value of66 07
.
- Evaluation: Determines how the match is evaluated. Evaluation can be a string, or lowercase-only string, numeric, or occurrence.
This measure lets you define different aspects of user actions to extract data based on action name and type as well as source and target page information. Use this measure for business transactions.
Select the check box for each field for which you want to create a splitting string, then enter a transformation regular expression to specify how to extract relevant information for each selected field. The include query and anchor as part of the URI check boxes let you further define the splitting string. Each of these check boxes apply to the fields above them.
This measure lets you use a regular expression to match a part of a URL used for splitting. Select a transformation regular expression from the list. The select expression displays based on the selected expression type. Select Custom to create your own regular expression.
Use this measure to create a split based on a specific Apdex Performance Zone by selecting the desired zone from the list.
- App Version: For mobile apps, this sets the value of
CFBundleShortVersionString
for iOS andversionName
for Android Apps that should be measured. For Web applications, this sets theappVersion
value for JS ADK or UEM settings. Select the App Version check box and select an operator from the list to indicate the relation to the entered app version. For example, selecting>="
and entering 6.0 in the text box indicates version 6.0 and later. - App Build (mobile apps only): Sets the value of
CFBundleVersion
for iOS andversionCode
for Android Apps that should be measured. Use this with App Version to set a specific build or build range within an app version. Select the App Build check box and select an operator from the list to indicate the relation to the entered build number. For example, selecting<="
and entering 632 in the text box indicates build 632 and earlier.
- Match: Select an operator from the list to indicate the type of matching and select or clear the Case Sensitive and Ignore Whitespaces to further define the match.
- Value: The value to match.
- Evaluation: Select the method used to evaluate the transformation regex from the list.
- Transformation Regex (optional): Enter a transformation regular expression to extract relevant information. The resulting value is the tagged expression or, if more expressions are present, the combination of all tagged expressions separated with a blank.
For example, a regex ID of(.\*)
and an input ofID=66
result in a value of66
. Also, a regex ID of([^_]*)_[^_]*_(.*)
and an input ofID=66_867_07
results in a value of66 07
.
- Detail Level: Select an operator from the list to indicate the level at which the Value is interpreted for the client. Detail levels include:
- Family: The browser or operating system family (for example, Windows, Firefox).
- Version: A specific to match (for example Windows 10, Chrome 60.0.3112.113).
- User Agent: The original User Agent string.
- Match: Select an operator from the list to indicate the type of matching and select or clear the Case Sensitive and Ignore Whitespaces to further define the match.
- Value: The value to match.
- Evaluation: Select the method used to evaluate the transformation regex from the list.
- Transformation Regex (optional): Enter a transformation regular expression to extract relevant information. The resulting value is the tagged expression or, if more expressions are present, the combination of all tagged expressions separated with a blank.
For example, a regex ID of(.\*)
and an input ofID=66
result in a value of66
. Also, a regex ID of([^_]*)_[^_]*_(.*)
and an input ofID=66_867_07
results in a value of66 07
.
- Target Page Title (optional): Select this check box to include a target page match in the splitting string based on the target page's title, then enter a transformation regular expression to extract the target page title split string. The resulting value is the tagged expression or, if more expressions are present, the combination of all tagged expressions separated with a blank.
- Target URI (optional): Select this check box to include a match of the target page in the splitting string, based on the target page's URI. Then enter a transformation regular expression to extract the target page title split string. The resulting value is the tagged expression or, if more expressions are present, the combination of all tagged expressions separated with a blank.
- Include query and anchor as part of the URI: Select this check box to further define the splitting string by including any query and anchor as part of the string.
This measure provides location information to be used in visits that are collected for analysis.
- Geographical granularity (Web Requests - Geo information): From the list, select the level of detail on which the client IP-address resolves into location information. If selecting Custom Regions from the list, you must add regions in the Regions enabled for table.
- Regions enabled for: Only appears when Custom Regions is set for Geographical granularity. Click Add to add a region entry, then on the entry line, select the desired country or continent from the list.
- Cities enabled for: Click Add to add a country or continent, then on the entry line select the desired country or continent from the list. To further define the entry, enter a number to indicate how many of the top cities in the country or continent to include for splitting.
- Match: Select an operator from the list to indicate the type of matching and select or clear the Case Sensitive and Ignore Whitespaces to further define the match.
- Value: The value to match.
- Evaluation: Select the method used to evaluate the transformation regex from the list.
- Transformation Regex (optional): Enter a transformation regular expression to extract relevant information. The resulting value is the tagged expression or, if more expressions are present, the combination of all tagged expressions separated with a blank.
For example, a regex ID of(.\*)
and an input ofID=66
result in a value of66
. Also, a regex ID of([^_]*)_[^_]*_(.*)
and an input ofID=66_867_07
results in a value of66 07
.
- Match: Select an operator from the list to indicate the type of matching and select or clear the Case Sensitive and Ignore Whitespaces to further define the match.
- Value: The value to match.
- Evaluation: Select the method used to evaluate the transformation regex from the list.
- Transformation Regex (optional): Enter a transformation regular expression to extract relevant information. The resulting value is the tagged expression or, if more expressions are present, the combination of all tagged expressions separated with a blank.
For example, a regex ID of(.\*)
and an input ofID=66
result in a value of66
. Also, a regex ID of([^_]*)_[^_]*_(.*)
and an input ofID=66_867_07
results in a value of66 07
.
- User Experience: Select a [User Experience Index]({# link_to_id id_how_does_uem_work #}#anchor_ueindex) value from the list to indicate the level visits are classified to.
- Match: Select an operator from the list to indicate the type of matching and select or clear the Case Sensitive and Ignore Whitespaces to further define the match.
- Value: The value to match.
- Evaluation: Select the method used to evaluate the transformation regex from the list.
- Transformation Regex (optional): Enter a transformation regular expression to extract relevant information. The resulting value is the tagged expression or, if more expressions are present, the combination of all tagged expressions separated with a blank.
For example, a regex ID of(.\*)
and an input ofID=66
result in a value of66
. Also, a regex ID of([^_]*)_[^_]*_(.*)
and an input ofID=66_867_07
results in a value of66 07
.
Calculation Measure Specific Attributes
The rate measure uses an existing base and a fraction measure to calculate a rate. You select the measures to use as the base and fraction measure.
- Base measure: Click Select and use the Select Measure dialog box to select an existing measure to use as the base measure reference for the Rate measure.
- Fraction measure: Click Select and use the Select Measure dialog box to select an existing measure to use as the fraction measure reference for the Fraction measure.
Threshold Violations Measure Specific Attributes
- Source Measure: Click Select Measure to select or create the source measure using the Select Measure dialog box.
- Threshold: Select the threshold level from the list.
User Action Health Measure Specific Attributes
Client Errors
- Severity (optional): Select an operator from the list to indicate how to match the logging level string, then enter the severity (containing the entered String) of the logging level.
- Name (Logging - count only- optional): Select an operator from the list to indicate how to match the logger name string, then enter the name of the logging measure.
- Message (optional): Select an operator from the list to indicate how to match the logger message string, then enter the logging measure message.
- Action Name, Action Type (optional): Use these attributes to specify how to match a user action to be measured, either by it's name or it's type. Select a match operator from the list, then enter the appropriate Action Name or Action Type. When using either of these attributes, only errors that match the action name or type are measured.
Use these attributes when you want to only measure browser errors that originate from a specific page.
- Page Title: Select an operator from the list to indicate how to match the title of the page or pages to be measured target.
- URI (optional): Select an operator from the list to indicate how to match the specified URI string.
- Query (optional): Select an operator to indicate how to match the specified query, then enter the query string.
- Anchor (optional): Select an operator to indicate how to match a page anchor string, then enter the anchor string. Using an empty anchor string
equals
as the operator matches only page calls without a declared URI.
Mobile Errors
- Mobile Error Type: Select the type of mobile error to capture for the measure. This determines the conditions that you use to define the errors to be collected for the specified error type.
- Conditions: Use conditions to further define how to match errors to be collected for the measure. You can use any of the Condition fields in combination, or specify no conditions to capture all errors of the error type. For each condition you want to define, select an operator from the list to indicate how to match the condition, then enter the condition.
User Actions Measures
- Action Name, Action Type (optional): Use these attributes to specify how to match a user action to be measured, either by it's name or it's type. Select a match operator from the list, then enter the appropriate Action Name or Action Type. When using either of these attributes, only errors that match the action name or type are measured.
- Action Name, Action Type (optional): Use these attributes to specify how to match a user action to be measured, either by it's name or it's type. Select a match operator from the list, then enter the appropriate Action Name or Action Type. When using either of these attributes, only errors that match the action name or type are measured.
These attributes let you collect user action data that starts or ends on a specific page or set of pages. Use the page title or URI, query and anchor information to define the match.
Use these attributes when you want to only measure browser errors that originate from a specific page.
- Page Title: Select an operator from the list to indicate how to match the title of the page or pages to be measured target.
- URI (optional): Select an operator from the list to indicate how to match the specified URI string.
- Query (optional): Select an operator to indicate how to match the specified query, then enter the query string.
- Anchor (optional): Select an operator to indicate how to match a page anchor string, then enter the anchor string. Using an empty anchor string
equals
as the operator matches only page calls without a declared URI.
Use these measures to create a user-defined identifier to collect timing W3C User Timings allow developers to create application specific timestamps for the browser's performance timeline. This includes the user-defined timing event types, mark and measure. mark events are named by the application and can be set at any location in an application. measure events application-named, but are placed between two marks to act as a midpoint between two marks. Use these measures to collect application specific timestamp data from an application. See the User Timing W3C recommendation page for more information about using performance interface extensions.
- Identifier for User Timing: Use this field to match the name of a mark or measure event name. This corresponds to the
name
parameter for marks, and themeasureName
parameter for measures. Select an operator list to define how you want to match, then enter thename
ormeasureName
. For example, to match performance marks declared inperformance.mark("mark-1")
,performance.mark("mark-2")
, andperformance.mark("mark-3")
, set the operator to starts with and entermark-
.
Mobile Actions
These measures collect user action data based on then name of an action, error, event, or a user-defined value.
- Action Name, Error Name, Custom Value Name, Event Name (optional): Select an operator from the list to indicate how to match the entered data, then enter the data to provide the match.
- Analyze only root actions: Select this check box to capture the high level root actions, based on any specified action name matching.
These measures let you capture specific mobile Web request timings, based on matching criteria for a specified mobile web page or set of pages, or HTTP response status codes that indicate whether a specific HTTP request has been successfully completed.
- URI, Response Code (optional): Select an operator from the list to indicate how to match a mobile page URI or HTTP response status code, then enter the URI or code to match on.
Page Actions
- Action Name, Action Type (optional): Use these attributes to specify how to match a user action to be measured, either by it's name or it's type. Select a match operator from the list, then enter the appropriate Action Name or Action Type. When using either of these attributes, only errors that match the action name or type are measured.
These attributes let you collect user action data that starts or ends on a specific page or set of pages. Use the page title or URI, query and anchor information to define the match.
Use these attributes when you want to only measure browser errors that originate from a specific page.
- Page Title: Select an operator from the list to indicate how to match the title of the page or pages to be measured target.
- URI (optional): Select an operator from the list to indicate how to match the specified URI string.
- Query (optional): Select an operator to indicate how to match the specified query, then enter the query string.
- Anchor (optional): Select an operator to indicate how to match a page anchor string, then enter the anchor string. Using an empty anchor string
equals
as the operator matches only page calls without a declared URI.
Use this measure when using the JavaScript ADK to extend the the JavaScript Agent default behavior. The ADK provides functions to report information to the Server, which then displays in the User Action PurePaths dashlet. Many of these functions require a key/value pair. This measure identifies the function based on matching the key for an ADK value to report specific information.
- Key for ADK value: Select an operator from the list to indicate how to match the key, then enter the ADK key. For example,
to collect data on user actions that contains a visit tag, set the operator to matches and enter
dt-visittag
.
These measures collect CDN or third party related information, including the number of CDN resources used and total duration used by CDN resources during a user action.
- Host: Can be used for filtering for specific hosts. Select an operator from the list to indicate how to match the host name, then enter then name of the host to filter by.
- Duration type (CDN and Third Party Content Load Time only): Several types of load times are available:
- Busy time: Time when at least one resource was loading.
- Average duration: The average duration of all resources.
- Shortest duration: The duration of fastest resource.
- Longest duration: The duration of slowest resource.
- Resource type: Valid selections include:
- All
- Images
- Scripts
- Stylesheets (only available with W3C Resource timing)
- Other resources (only available with W3C Resource timing)
- Custom resources (resources added by the ADK)* Host:
- Resource State (CDN and Third Party Content Count only): Select a specific state from the list to only find CDN or third party content. You can keep the default selection (all states), or include only failed, successful, interrupted, or cached resources.
- Media Type: Select the type of streaming media being watched or listened to.
- Media URL: Select an operator to indicate how to match the specified URL containing the streaming media, then enter the URL.
- Action Name, Action Type (optional): Use these attributes to specify how to match a user action to be measured, either by it's name or it's type. Select a match operator from the list, then enter the appropriate Action Name or Action Type. When using either of these attributes, only errors that match the action name or type are measured.
These attributes let you collect user action data that starts or ends on a specific page or set of pages. Use the page title or URI, query and anchor information to define the match.
Use these attributes when you want to only measure browser errors that originate from a specific page.
- Page Title: Select an operator from the list to indicate how to match the title of the page or pages to be measured target.
- URI (optional): Select an operator from the list to indicate how to match the specified URI string.
- Query (optional): Select an operator to indicate how to match the specified query, then enter the query string.
- Anchor (optional): Select an operator to indicate how to match a page anchor string, then enter the anchor string. Using an empty anchor string
equals
as the operator matches only page calls without a declared URI.
These measures use W3C resource timing API to capture resource timings in the browser.
- URL: Select an operator to indicate how to match the specified URL for which you want resource timings.
- Category: Select whether to capture first party, CDN, or third party timings.
- Resource type: Valid selections include:
- All
- Images
- Scripts
- Stylesheets (only available with W3C Resource timing)
- Other resources (only available with W3C Resource timing)
Visits measures
- Action Name, Action Type (optional): Use these attributes to specify how to match a user action to be measured, either by it's name or it's type. Select a match operator from the list, then enter the appropriate Action Name or Action Type. When using either of these attributes, only errors that match the action name or type are measured.
Use the Conversion count measure to get a count of to include only visits that are converted by specific conversion goals. No conversion goals specified for the measure means all conversion goals are used. Click Add and use the [Select Measure] dialog box to select conversion-goal measures to include. Added gonversion goal measures appear in the table's Conversion Goal column.