Page tree
Skip to end of metadata
Go to start of metadata

BMC Real End User Experience Monitoring Software Edition provides the following system custom fields, which have customizable data sources, traffic selection, and transformations:

  • Object custom fields collect attributes and metrics specific to objects.
  • Page custom fields collect attributes and metrics specific to pages, and usually pull their information from the objects within these pages using the first, last or all occurrences or the entry or exit points.
  • Session custom fields collect metrics and statistics specific to sessions and retrieve their information from either the pages or objects below them.
  • Primitive custom fields exist on the Real User Collector and hardware devices and extract data from the headers and content of HTTP requests and responses.

For any type of custom field, the system collects data first and then applies transformations or extraction rules. Because various reports and screens within the system use them, these fields must remain available, so you cannot delete or turn them off.

The following tables describe system custom fields.

Object custom fields

Field name

Grammar name

Export name

Description

Page ID

page_id

page-id

Unique identifier of a page. All objects sharing this ID are assembled under the same page.

Server ID

server_id

x-server-id

Identifier of the server or network infrastructure component that serviced the request

Trace

trace

trace

The value for this custom field is extracted from the HTTP response of the Application Visibility primitive custom field.


Page сustom fields

Field name

Grammar name

Export name

Description

Application Name

application_name

x-application-name

Web application as defined by the user

Browser Name

browser_id

browser

Browser that the client uses

OS

os

os

Client's operating system

Page Name

page_name

x-page-name

Page as defined by the user

Page Referrer

page_referrer

x-custom-referrer-name

Referring page

Trace

trace

trace

The value for this custom field is extracted from the HTTP response of the Trace object custom field.

Session custom fields

Field name

Grammar name

Export name

Description

Browser Name

None

x-custom-browser

Browser that the client uses

Entry Page Name

None

x-custom-entry-page

Entry page associated with this session

Exit Page Name

None

x-custom-exit-page

Exit page associated with this session

Site Referrer

None

x-custom-referrer-domain

URL of the referrer to the first page in the session

User ID

None

x-user-id

Token extracted from traffic. You can use it to associate a session with a specific user.


Primitive custom fields

Field name

Grammar name

Export name

Description

Application Visibility

application_visibility

applicationVisibility

In the default configuration, the value for this primitive custom field is extracted from the response header.

Browser Name

browser_id

browser

Browser that the client uses

First Public IP

first_public_ip

x-first-public-ip

The public IP address (IPv4 only) closest to the browser and the one used to look up geographic information.

OS

os

os

Client's operating system

Web Server IP

web_server_ip

web_server_ip

The IP address of the web server (IPv4 only). This address can be different from the server IP when the TCP connection is terminated on a proxy. The system populates this field only if a confirmed web server responds to the HTTP request.

Note

Primitive is the only type of custom field that can pull information from the HTTP headers and content. For example, you can use a particular header for object type detection, or collect special content for page building.

You can use the data from primitive custom fields only with the grammar name on the Analyzer component. Use the export name only when you export from the Collector component to another application.

Related topics

Using custom fields to filter traffic, export data, or monitor error conditions

Defining traffic extraction rules on the Analyzer