A New Relic Java Agent extension that provides the ability to add custom instrumentation around the J2EE javax.servlet.http.HttpServlet#service() method.

Historical Note: Historically this extension only provide the naming functionality, which is why the extension is named 'HTTPServlet-transaction-namer'.

To install:

1. Download the latest release jar files.
2. In the New Relic Java directory (the one containing newrelic.jar), create a directory named extensions if it does not already exist.
3. Copy the downloaded jars into the extensions directory.
4. Restart the application.
5. Add the appropriate settings to newrelic.yml as described in the Configuration section.
6. Restart your JVM
7. After the app has reloaded, generate traffic against your app that will trigger transactions that you expect to see renamed.
8. To debug issues, set log_level to finer in newrelic.yml.

By default, the built-in TransactionNamer instrumentation is registered. This instrumentation can be used to alter the way in which the Transaction name is set for a Servlet request.

All configuration of this extension is done in newrelic.yml or alternatively, via java properties.

1. You must disable auto transaction naming. Find the parameter called enable_auto_transaction_naming and set it to false.
2. Enable the extension you copy the YAML snippet from the configuration template below and paste it within the common: section of the newrelic.yml. Note: It can be anywhere within the common section (for example, below the app_name parameter).
3. See the renaming options to determine which to use.
4. Ensure that the indentation levels of the httpservlet_transaction_namer section match exactly to the way they appear in the template below. Every indentation in YAML is 2 spaces (NOT tabs). The httpservlet_transaction_namer: line should have exactly 2 spaces in front of it, the next line should have 4, and so on.

  httpservlet_transaction_namer:
    instrumentations:
      - com.newrelic.fit.javax.servlet.http.TransactionNamer
    append_parameters:
      enabled: true
      parameters:
        - name: categoryId
          type: parameter
        - name: host
          type: header
    name_grouper:
      enabled: true
      patterns:
        - '(\/wps\/myportal\/[^!]*)!ut.*'
        - '(\/jpetstore_web\/[^.]*)\..*'
        - '(\/jpetstore_web\/accounts\/)[^\/]+\/(.*)'
    name_obfuscator:
      enabled: true
      patterns:
        - '/AncillaryApplication/<recLoc>/<lastName>'
        - 'AncillaryApplication/<recLoc,\w{3}>/<lastName,\w+>'
        - '/Ancillary\w+/<recLoc,\w{3}>/<lastName>'
        - '(?<obfuscatedVin>[A-Za-z\d]{11}\d{6})'

By default, the built-in TransactionNamer instrumentation is registered with the extension. This instrumentation can be used to alter the way in which the transaction name is set for a Servlet request. The TransactionNamer provides 3 mechanisms for altering the transaction name:

1. append_parameters - Renaming based on HTTP parameters/cookies/headers
2. name_grouper - Grouping transaction names
3. name_obfuscator - Obfuscating transaction names
4. Custom instrumentation

Use append_parameters to rename Transactions using HTTP parameters, cookies & headers. You can append any HTTP request parameter, cookie or header to the transaction name.

    append_parameters:
      enabled: true
      parameters:
        - name: [parameter_name]
          type: [cookie|header|parameter]
        - name: [parameter_name]
          type: [cookie|header|parameter]

• Valid values for transaction_parameter_type are cookie, header and parameter.
• You can append as many parameters as you want. Each one gets its own list member (signified by a -), name and type.
• The parameters will be appended in the order in which they are listed.

Use name_grouper to group your transactions into names from URL segments. Using regular expression patterns, choose which URLs to analyise and the segments by which you want to group transations.

    name_grouper:
      enabled: true
      patterns:
        - 'pattern 1'
        - 'pattern 2'
        - 'pattern 3'

• The patterns are regex patterns that are matched against the URI.
• Each pattern must be on it's own line, surrounded by single-quotes.
• Use normal Java regular expressions as the pattern.
  • Great tutorial/reference for regex: http://www.regular-expressions.info/
  • Regex building tool: http://www.regexr.com/
• For any segment you wish to preserve, use a regex grouping (like this).
• For any segment you wish to group by, do NOT put it in a regex grouping. It will simply not appear in the resultant transaction name.
• Each URI will be successfully matched only once - subsequent patterns that would match that URI will not be tested.

Pattern 1: Group WebSphere Portal transactions without Stateful URL string

• Pattern: (\/wps\/myportal\/[^!]*)!ut.*
• Matches the following URLs:
  • /wps/myportal/Search/Search%20Center/!ut/p/a1/04_Sj9CPykssy0xPLMnMz0vMAfGjzOKd3R0
  • /wps/myportal/tagging/!ut/p/a1/04_Sj9CPy328dh23ch249fho2ij1jKJ8x9T
• Groups these URLs as:
  • /wps/myportal/Search/Search%20Center/
  • /wps/myportal/tagging
• Does NOT match the following URLs:
  • /wps/portal/Search/Search%20Center/!ut/p/a1/04_Sj9CPykssy0xPLMnMz0vMAfGjzOKd3R0
  • /wps/myportal/tagging/some/other/stuff

Pattern 2: Strip extensions from URI (.jsp, .html, etc.)

• Pattern: (\/jpetstore_web\/[^.]*)\..*
• Matches the following URLs:
  • /jpetstore_web/catalog/Item.jsp
  • /jpetstore_web/help.html
• Groups these URLs as:
• /jpetstore_web/catalog/Item
• /jpetstore_web/help
• Does NOT match the following URLs:
  • /jpetstore_web/catalog/Checkout
  • /jpetstore_notweb/catalog/Item.jsp

Pattern 3: Combine transactions from different subdirectories (i.e. per-account settings)

• Pattern: (\/jpetstore_web\/accounts\/)[^\/]+\/(.*)
• Matches the following URLs:
  • /jpetstore_web/accounts/account1/editAccount
  • /jpetstore_web/accounts/another_account/doEdit
• Groups these URLs as:
  • /jpetstore_web/accounts/editAccount
  • /jpetstore_web/accounts/doEdit
• Does NOT match the following URLs:
  • /jpetstore_web/accounts/noaccount
  • /jpetstore_notweb/accounts/account1/editAccount

Use name_obfuscator to obfuscate URL segments in Transaction Names. Using regular expression patterns, choose which URLs to analyise and which segments will be masked AND grouped together.

    name_obfuscator:
      enabled: true
      patterns:
        - 'pattern 1'
        - 'pattern 2'
        - 'pattern 3'

• For any segment you wish to obfuscate, use <replacement_name>, in which replacement_name is the name you want to group that segment as, for example <lastName>.
• For any segment you wish to obfuscate AND it requires a regex statement to collect, use the following notation: <replacement_name,regex>.
• Each pattern must be on it's own line, surrounded by single-quotes.
• You can use normal Java regular expressions anywhere in the pattern, even outside of obfuscated fields.
  • Great tutorial/reference for regex: http://www.regular-expressions.info/
  • Regex building tool: http://www.regexr.com/

Pattern 1: Basic pattern match using <replacement_name> notation in URL pattern

• Pattern: '/AncillaryApplication/<recLoc>/<lastName>'
• Matches the following URLs:
  • /AncillaryApplication/92Jets/Selanne
  • /AncillaryApplication/Helsinki/Kurri17
• Groups these URLs as: /AncillaryApplication/<recLoc>/<lastName>
• Does NOT match the following URLs:
  • /AncillaryApplication/92Jets/Selanne/Teemu
  • /NotAncillaryApplication/Turku/Koivu

Pattern 2: Using <replacement_name,regex> notation in URL pattern

• Pattern: 'AncillaryApplication/<recLoc,\w{3}>/<lastName,\w+>'
• Matches the following URLs:
  • /AncillaryApplication/HEL/Kapanen
  • /AncillaryApplication/KUO/Timonen
• Groups these URLs as: /AncillaryApplication/<recLoc>/<lastName>
• Does NOT match the following URLs:
  • /AncillaryApplication/Helsinki/Tikkanen
  • /AncillaryApplication/OUL/Pitkanen25

Pattern 3: Using regex elsewhere in URL pattern

• Pattern: '/Ancillary\w+/<recLoc,\w{3}>/<lastName>'
• Matches the following URLs:
  • /AncillaryApplication/TMP/Numminen grouped as /AncillaryApplication/<recLoc>/<lastName>
  • /AncillaryApp/TKU/Salo grouped as /AncillaryApp/<recLoc>/<lastName>

Pattern 4: Replace regex pattern everywhere in URL path

• Pattern: '(?<obfuscatedVin>[A-Za-z\d]{11}\d{6})'
• Matches the following URLs:
  • /VehicleApplication/AB1CDE2EFGH567890 grouped as /VehicleApplication/<obfuscatedVin>
  • /VehicleApplication/AB1CDE2EFGH567890/AnotherSegment/IJ1KLM2NOPQ567890/TheEnd grouped as /VehicleApplication/<obfuscatedVin>/AnotherSegment/<obfuscatedVin>/TheEnd

The most recent Java agent versions have introduced constraints on altering agent attributes. This makes it necessary to exclude the "request.uri" attribute and utilize the obfuscated "custom.request.uri" instead. To apply this change, navigate to the newrelic.yml file, locate the "attributes" section, and modify the "exclude" parameter as described below:

 # Provides the ability to configure the attributes sent to New Relic. These
 # attributes can be found in transaction traces, traced errors,
 # transaction events, and page views.
 attributes:

  # When true, attributes will be sent to New Relic. The default is true.
  enabled: true 
  #A comma separated list of attribute keys whose values should
  # be sent to New Relic.
  #include: 

  # A comma separated list of attribute keys whose values should
  # not be sent to New Relic.
  exclude: request.uri

Additional custom instrumentations can be created as follows.

1. Create a class that implements the ServletInstrumentation interface. The Javadoc for this interface is included with the distribution package.
   1. Implement the init(Config config) method. This method is called only once throughout the lifetime of the parent class loader. Use this time to initialize any private variables based on the Agent configuration in config.
   2. Implement the instrumentRequest(request, response, agent, config) method. This method is called once for every servlet request. Logic contained in this method should consume as few compute resources as possible since it is called frequently.
2. Ensure that the compiled class file for you class is present on the application server CLASSPATH. Mechanisms for this vary and are outside the scope of this documentation.
3. Register the custom instrumentation by updating the New Relic Java agent configuration (newrelic.yml) as follows.
   1. Locate the custom.httpservlet_transaction_namer.instrumentations property in the YML.
   2. Add a new line with proper indentation that contains the - prefix and the fully-qualified class name of the custom class. E.g.

      httpservlet_transaction_namer:
        instrumentations:
         - com.newrelic.fit.javax.servlet.http.TransactionNamer
         - path.to.my.package.CustomInstrumentation

   3. Add any other configuration necessary for the custom instrumentation within the httpservlet_transaction_namer container in the YAML. E.g.

      httpservlet_transaction_namer:
      ...
        my_custom_stuff:
          foo: bar
          list:
           - 1
           - 2

   The custom instrumentation can access this data through the config parameter in the init(config) method.
4. Restart your JVM and your extension should be available.

If you make changes to the instrumentation code and need to build the instrumentation jars, follow these steps

1. Set environment variable NEW_RELIC_EXTENSIONS_DIR. Its value should be the directory where you want to build the jars (i.e. the extensions directory of the Java Agent).
2. Build one or all of the jars.
   a. To build one jar, run the command: gradlew httpservlet-transaction-namer:clean httpservlet-transaction-namer:install
   b. To build all jars, run the command: gradlew clean install
3. Restart the application

There is a test gradle target defined for this project that runs JUnit tests.

New Relic has open-sourced this project. This project is provided AS-IS WITHOUT WARRANTY OR DEDICATED SUPPORT. Issues and contributions should be reported to the project here on GitHub. We encourage you to bring your experiences and questions to the Explorers Hub where our community members collaborate on solutions and new ideas.

We encourage your contributions to improve HTTPServlet Transaction Namer! Keep in mind when you submit your pull request, you'll need to sign the CLA via the click-through using CLA-Assistant. You only have to sign the CLA one time per project. If you have any questions, or to execute our corporate CLA, required if your contribution is on behalf of a company, please drop us an email at [email protected].

A note about vulnerabilities

As noted in our security policy, New Relic is committed to the privacy and security of our customers and their data. We believe that providing coordinated disclosure by security researchers and engaging with the security community are important means to achieve our security goals.

If you believe you have found a security vulnerability in this project or any of New Relic's products or websites, we welcome and greatly appreciate you reporting it to New Relic through HackerOne.

HTTPServlet Transaction Namer is licensed under the Apache 2.0 License.