Adding a primitive custom field


You can configure a custom field that captures data from request and response headers and content for later use in reports, Watchpoints, and other system entities.

The macro unmigrated-inline-wiki-markup from Confluence is no longer available.

To add a primitive custom field

  1. In a

    The macro unmigrated-inline-wiki-markup from Confluence is no longer available.

    , point to the Administration > Data flow settings, and then click Custom fields.
  2. On the Action menu, click Create new primitive custom field.
  3. In the Field name and Description boxes, enter a name and a description for the new field.
  4. In the Grammar name box, type the name to use to access the new field through the system's Watchpoint filter grammar.
     You can use this grammar name to create filters or Watchpoints with the new field.
  5. In the Export name box, enter the name to use to access the new field through the system data export feature.
     This name will appear in the header of any export file containing the field.
  6. In the Expected data type list, select the data type that you want the system to validate your field with.
     This specification ensures that you do not see a string when expecting a number, or a decimal number when expecting an IP address.
  7. In the Final output size limit box, enter the maximum number of characters for the field output (additional characters are truncated).
  8. Click Save.

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

Related topic

Adding-an-extraction-rule-to-a-custom-field

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*