topic RUM data is not reporting in the application in Real User Monitoring

RUM data is not reporting in the application

ainhoa_martinez — Wed, 17 Nov 2021 14:51:21 GMT

A través del F12 detectamos ruxitagentjs (etiqueta JavaScript que Dynatrace OneAgent inserta automáticamente).

El método GET HTTP 403 nos devuelve  Significa que no tenemos permisos para acceder a [directorio] en ese servidor.

¿Necesitamos saber qué reglas nos pueden estar bloqueando en la capa de acceso, o por el contrario, poder permitir alguna regla en la capa de acceso para que podamos acceder?

Re: Firewall constraints for RUM. RUM data is not reporting in the application

MaciejNeumann — Wed, 15 Sep 2021 13:34:08 GMT

Translation to English, from Google Translate:

Through F12 we detect ruxitagentjs (JavaScript tag that Dynatrace OneAgent inserts automatically).

The GET HTTP 403 method returns  It means that we do not have permissions to access [directory] on that server.

Do we need to know what rules may be blocking us in the access layer, or on the contrary, to be able to allow some rule in the access layer so that we can access?

Re: Firewall constraints for RUM. RUM data is not reporting in the application

Christophe_N — Fri, 17 Sep 2021 12:47:46 GMT

Hi,

If you have some firewall , you may check this article : https://www.dynatrace.com/support/help/how-to-use-dynatrace/real-user-monitoring/setup-and-configuration/web-applications/initial-configuration/firewall-constraints-for-rum/?_ga=2.152631801.1513930615.1631515564-779904236.1616147976#request-headers

Firewall rules needs to allow the user's browser access to your tenant (or AG?) for sending those RUM infos.

Regards,

Christophe