Firewall constraints for RUM (original) (raw)

9min

Real User Monitoring (RUM) uses HTTP technologies to send performance data from your end users' browsers to Dynatrace. To do this, the RUM JavaScript is injected into your application's webpages. This tag or code snippet communicates with Dynatrace. However, you must verify the configuration of your firewalls, proxies, and web servers to allow all required data to pass through.

Requests

For RUM to function fully, the following HTTP requests must pass through your infrastructure:

Requests for the RUM monitoring code.
- In case of agentless monitoring, these requests are sent to the Dynatrace CDN with a URL that contains the string js-cdn.dynatrace.com/jstag/.
- In case of auto-injection, they are, by default, sent to the web or app server that hosts the application, and their URL path contains the string ruxitagentjs_.
  For details on the default URL and the available configuration options, see Configure the Real User Monitoring code source.
RUM beacons reporting the data captured by the RUM JavaScript back to Dynatrace.
- In case of agentless monitoring, beacons are, by default, sent to a beacon endpoint that is part of the Dynatrace SaaS infrastructure. The URL path is /bf or /bf/<id>.
- In case of auto-injection, beacons are, by default, sent to the web or app server that hosts the application, and the URL contains the string /rb_<id>.
- The beacon URL contains query parameters. Ensure that your firewall does not remove any query parameters.
- The POST body contains the payload. The payload is sent with the text/plain content type. For Session Replay, the application/octet-stream content type can also be used.
  For the available beacon endpoint configuration options, see Configure beacon endpoint for web applications.

RUM uses the following HTTP headers. All of these headers must be able to reach Dynatrace.

Used for transaction stitching in HTTP headers. Set by OneAgent to link web servers. Ensure that network components, such as firewalls and routers, are never configured to remove these headers. Incorrect configuration can potentially lead to broken distributed traces. Some network components disable such requests and throw a 403 HTTP error, which is why it is necessary to configure these components to accept the x-dynatrace header.

Contains the ID of the RUM application, the cookie domain, and the injection rule (noop, auto, before, or after). Also contains the injection pattern when injectionRule=after or injectionRule=before.

Used in case there's some proxy in between a user's browser and the original process that delivers the page.

Preserves the original URL of the request in case of URL rewriting.

Tracks the depth of a subpath tree to avoid endless distributed traces.

Identifies proper endpoints for beacon transmission; includes session ID for correlation.

Contains the referer of the page for an action and improves the correlation results.

Contains information for correlation of cross-origin XHRs.

Sets the dtCookie cookie in case the HTTP request doesn't contain any.

Used to track proxy scenarios by the NGINX code module.

X-ruxit-Apache-ServerNamePorts

Used by the Apache code module to synchronize service naming with the PHP code module.

Used by the IIS code module to declutter .NET code module subpaths.

Discarded by the Apache code module during the fine-tuning of HTML injection behavior.

Discarded during the fine-tuning of HTML injection behavior.

Discarded when caching is suppressed.

Modified when caching is suppressed.

Contains the address of the previous web page from which a link to the currently requested page was followed.

Contains the host information on non-http(s) domains.

Confirms that the RUM JavaScript has been injected to avoid duplicate injection.

Has one of the following values:

true: the injection has been completed.
block: the injection must not be attempted at this time.

Confirms that the RUM JavaScript has been injected to avoid duplicate injection.

Has one of the following values:

true: the injection has been completed.
block: the injection must not be attempted at this time.

Contains the results of the RUM JavaScript injection diagnostics performed by Dynatrace Support.

If the RUM health check is enabled, any involved OneAgent code module adds its ID here. Set for responses to special requests.

Contains the fully qualified name of the injected servlet or filter.

Sets the session state cookie of OneAgent.

OneAgent appends a custom string to the original ETag response header to track the changes in the application configuration.

If the ETag response header is manipulated, OneAgent also subtracts 1 second from the original value of this header. Set for responses to special requests.

Adapted upon HTML injection. Set for responses to special requests.

Adapted during HTML injection into compressed responses. Set for responses to special requests.

Adapted during HTML injection into compressed responses.

Set for responses to special requests.

Access-Control-Allow-Origin

Set for responses to special requests.

Used to transport information that is relevant for RUM correlation.

Allows the RUM JavaScript to access the information that is relevant for RUM correlation in case of cross-origin requests.

Access-Control-Allow-Headers

Set for responses to special requests.

Access-Control-Allow-Methods

Set for responses to special requests.

Cookies

RUM uses the following cookies. All of these must be able to reach Dynatrace. See Cookies for more information on how Dynatrace uses cookies.

No set limitation, but usually less than 100 B

Tracks a visit across multiple requests.

Measures server latency for performance monitoring.

Identifies proper endpoints for beacon transmission; includes session ID for correlation.

Serves as an intermediate store for page-spanning actions.

Length of dTValidationCookieValue string, that is 23

Determines the top-level domain.

Determines if the RUM JavaScript should be deactivated due to cost and traffic control or overload prevention.

rxVisitor<cookie_suffix>1

Contains the visitor ID to correlate sessions.

Includes the timestamp of the session timeout.

Mobile RUM

OneAgent for Mobile uses the x-dynatrace header for tagging HTTP requests. Dynatrace uses this header to link the mobile part of the web request to the service part captured by another OneAgent.

For hybrid applications, the dtAdk cookie allows to join a session from OneAgent for Mobile and a session from the RUM JavaScript so that these sessions appear as a single session, while the dtAdkSettings cookie is used for syncing settings between OneAgent for Mobile and the RUM JavaScript.

/mbeacon is the monitor signal that OneAgent for Mobile sends back to Dynatrace if the data is transferred through ActiveGate. If the data is sent to another OneAgent, the monitor signal is /dtmb.