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

This procedure describes how you can configure a custom field that captures the object data that you can use in Watchpoints and other system entities. To perform this procedure, you must have Operator-level access, or higher.

To add an object custom field

  1. In a Real User Analyzer, point to the Administration > Data flow settings, and then click Custom fields.

  2. On the Action menu, click Create new object custom field.
  3. In the Field name and Description boxes, enter a name and a description for the new field.
  4. (Optional) To create equivalent custom fields for parent pages or sessions automatically, select the relevant Inheritance of parent records check boxes.
  5. In the Grammar name text box, enter the name that you want to use to access the new field through the system's Watchpoint filter grammar.
    You can use this grammar name to filter Watchpoints that use custom fields
  6. In the Export name field, enter the name to use to access the new field through the system data export feature.
    This name appears in the header of any export file containing the field.
  7. In the Expected data type list, select the data type you want the system to validate your field with.
    This specification ensures that you do not see a string when you expect a number, or a decimal number when you expect an IP address.
  8. In the Final output size limit box, enter the maximum number of characters for the field output (additional characters are truncated).
  9. Click Save.

    The system creates an object custom field. Now you can add an extraction rule to this custom field.


When you create an object custom field, you can create equivalent page and session custom fields automatically. Similarly, when you create a page custom field, you can automatically create an equivalent session custom field. These automatically created custom fields are known as inherited custom fields. You can create them only when you create the original custom field.

An inherited custom field uses the same grammar name identifier as its parent and shares other settings. To change a custom field setting but not affect the field created by inheritance, you must first break the connection by changing the grammar name of either the inherited field or the parent field.

Related topics

Adding custom fields on the Analyzer

Adding an extraction rule to a custom field