Our vBulletin migration is complete.
Welcome vBulletin users! All content and user information from the Micro Focus Forums (vBulletin) site has been migrated to this site. READ MORE.

[APM] RUM Transaction configuration for parallel, out-of-order actions/pages

[APM] RUM Transaction configuration for parallel, out-of-order actions/pages

APM RUM transaction configuration lacks the possibility of recognizing complex transactions which include adjacent, out-of-order actions/pages.

We would like to be able to customize transaction definition so that, given a set of named pages (P1...PN), only transactions following these rules are registered:

  1. P1 and P2 are accessed in order;
  2. P3 to PN are accessed in ANY order;
  3. only named pages are included (P1 to PN).

In some of our scenarios, when microservices are concerned, information is accessed and retrieved through parallel, out-of-order HTTP requests. However, with the current configuration options, it's not possible to set up a correct monitoring.

1 Comment
Micro Focus Expert
Micro Focus Expert
Status changed to: Waiting for Votes

Could you explain the correlation between microservices and out-of-order http request for your specific application. What's the technology used for your application, is this a single page application - like Angular?

The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.