Add a Sensitive URL Filter

You can use sensitive URL filters to configure the agent to obfuscate sensitive information from the URLs in transaction snapshot details.
Add a sensitive URL filter element as a child of the sensitive URL filters element:
CODE 
<sensitive-url-filter delimiter="..."
                                  segment="..."
                                  match-filter="..."
                                  match-pattern="..."
                                  param-pattern="..."/>
  • segment : Specify a comma-separated list to indicate the segments that you want the agent to filter. Segment numbering starts from 1.
  • match-filter : Specify the type of filtering to be used to match the url. Allowed values are EQUALS, INLIST, STARTSWITH, ENDSWITH, CONTAINS, REGEX and NOT_EMPTY. Default is NOT_EMPTY.
  • match-pattern : Specify the string that you want to be filtered by the match-filter .
  • param-pattern : Specify the regular expression matching the query parameters to filter.

  • delimiter : Specify the character that you want to use as URL segment endpoints. The agent splices the URL at each delimiter instance to create the segments. For HTTP, use the forward slash character "/".

    Warning: The indexing starts from 1 and that the protocol names (http://, https://, ...) are not treated as special cases, so for URLs containing protocol: http://myapp.example.com/sensitive/data?first_name=abc&last_name=xyz the segments are:
    • http:
    • ""
    • myapp.example.com
    • sensitive
    • data
For example, the following configuration splits the URL on the "/" character and masks the fourth segment and the param-pattern in the third segment of the URL. In this case, the segmentation and obfuscation apply only to URLs containing "myapp".
CODE 
<sensitive-url-filter delimiter="/"
                                  segment="4"
                                  match-filter="CONTAINS"
                                  match-pattern="myapp"
                                  param-pattern="[a-z]+_name"/>
The exit call to https://myapp.example.com/sensitive/data?first_name=abc&last_name=xyz breaks down to three segments:
  • https://myapp.example.com/
  • sensitive
  • data?first_name=abc&last_name=xyz
The Controller shows the masked values of the URL and the param-pattern display https://myapp.example.com/*****/data?first_name=***&last_name=*** in the snapshot details.
Note: In case you do not use any values for the query parameters, the Controller does not mask any query parameters in the URL.