Page groups do not seem to aggregate

fstekelenburg — Mon, 06 Dec 2021 10:00:18 GMT

We have a customer with an application with urls that contains session IDs.

e.g. /module/(s(#LONG ID HERE#))/action/page

In the naming rules of load and XHR actions the replacement of the IDs work fine.
e.g. /module/(s(*ID*))/action/page

So on the application dashboard the (Top 3) user actions are cleaned from the IDs.

However the pages and page groups, as seen in the Top 3 pages and Top errors contain long lists of the same pages with all the IDs, where I would expect page grouping would aggregate. Is this by design? I can not see how we can control this from within managed. Using RUM JavaScript API, manually instrument the index.js file for the web application isn't an option at this point.

Page groups

Name
/module/(s(12345678901234567890))/action/page
/module/(s(34567890123456789012))/action/page
/module/(s(56789012345678901234))/action/page
/module/(s(78901234567890123456))/action/page
/module/(s(90123456789012345678))/action/page

Re: Page groups do not seem to aggregate

ChadTurner — Wed, 08 Dec 2021 02:12:43 GMT

That's a good Question. Hopefully someone from Dynatrace can provide some clarity on this

Re: Page groups do not seem to aggregate

Julius_Loman — Sun, 12 Dec 2021 15:55:50 GMT

AFAIK the only control at the moment is to push the information using the dtrum JS API where you can set the name:

setPage(newPage: APIPage): number

topic Re: Page groups do not seem to aggregate in Real User Monitoring

Page groups do not seem to aggregate

Re: Page groups do not seem to aggregate

Re: Page groups do not seem to aggregate