Using the instructions below, you can begin to match your CloudTest transactions by name to Tagged Web Requests in dynaTrace. All that is required is inserting a custom header in the request.
The end goal is to see your custom names listed in both tools.

After doing some research on the Soasta forums and running multiple experiments, I came up with the following header that will satisfy the required and optional components of the dynaTrace header.

The Header Statement

The header consists of four elements which we populate using CloudTest’s In Situ Substitution Expressions (ISSE):

  • VU=
    • We use the VUNumber expression to return the Virtual User Number of the transaction execution.
  • PC=
    • This is the Page Context. While you can substitute many other ISSE’s in place of this one, I’ve opted to use the messageName. Assuming you do not modify the message name, the message name will be an indicator of the page you are actually calling, such as ‘orange.jsf’. It’s a good idea to map this to some page context like this so you can match back up to the actual web request when necessary.
  • ID=
    • This is a unique identifier. Fortunately, Soasta can run javascript on the fly, so here we use the javascript method new Date().getTime() This method returns the number of milliseconds since midnight Jan 1, 1970. Used in conjunction with VU, ID and NA, it will ensure a unique tag for each request.
  • NA=
    • NA is perhaps the most important. This is where you connect your CloudTest transaction name to the dynaTrace Tagged Web Request name. You’ll have to decide which CloudTest element you want to associate it with, a Transaction name, Page name, group, chain, etc.
    • In the example above, we’re using currentPage.name. However, some likely alternatives include:
      • Page Name: {%% expr: $context.currentPage.name %%}
      • Transaction Name: {%% expr: $context.currentTransaction.name %%}
      • Group Name: {%% expr: $context.currentGroup.name %%}
      • Chain Name: {%% expr: $context.currentChain.name %%}
      • Message Name: {%% expr: $context.currentMessage.name %%}

Placing the Header

More advanced users may find a way to place this header once and have it dynamically generated with every request, but my knowledge of Soasta Cloudtest limited me to manual placement in every request.

To place the header (refer to screenshot below):

  • Select the Message element and click on Selected:[element name] in the lower panel.
  • When the selected message properties are displayed, click on “HTTP Header Requests.”
  • The HTTP Request Headers will appear on the right of the lower panel. Simply paste your header in this panel and save your work.

More information
Further details of how to integrate your load testing or monitoring tool with dynaTrace can be found here: Integration with Web Load Testing and Monitoring Tools