Ignore user action naming rules with

Romanenkov_Al3x — Fri, 14 Apr 2023 11:38:46 GMT

Hello.

UPD: The main reason was - outdated JS oneagent version on some frontend servers.

A very important rule is to check for errors on the latest version. In many cases, as in this, everything was resolved.

We have application with dtrum instrumented on frontend.

Some actions got names with "dtrum.actionName" call.

For some reasons update 238 version -> 240 version dramatically broken down dashboards \ metrics \ key user actions - because something with default action naming rules changes in Dyna...

IN General:

Customer USES dtrum.actionName and manual instrumenting to AVOID any problems with "user action naming rules changes" but have faced with changes on platform layer during update (238-240)

The main question is:

Can we add additional properties to JS agent - to have IGNORE user ANY action naming rules defined and get exactly frontend developers defined in "dtrum.actionName" function.

Is there any additional flags - which we can use to tell Dynatrace use OLD approach (238 version)...

Regards,

Romanenkov Alex

Re: Ignore user action naming rules with

ChadTurner — Thu, 13 Apr 2023 13:17:31 GMT

@Romanenkov_Al3x I would put in a RFE for this especially if it broke your previous functionality

Re: Ignore user action naming rules with

Romanenkov_Al3x — Fri, 14 Apr 2023 11:38:02 GMT

UPD: The main reason was - outdated JS oneagent version on several frontend servers.

A very important rule is to check for errors on the latest version. In many cases, as in this, everything was resolved.

Regards,

Alex Romanenkov

topic Ignore user action naming rules with in Real User Monitoring

Ignore user action naming rules with

Re: Ignore user action naming rules with

Re: Ignore user action naming rules with