Normally you benefit from Real User Monitoring only after you’ve installed Dynatrace OneAgent. Agentless monitoring is meant to be used in cases that you don't have access to your web server and therefore you cannot install OneAgent. Otherwise installation of Dynatrace OneAgent is recommended for the following reason:
To enable agentless real user monitoring, follow the steps outlined below.
Before you begin
What you'll need:
Set up agentless monitoring
Select Deploy Dynatrace from the navigation menu and then click Set up agentless or AMP monitoring. You can alternatively select Applications from the navigation menu, click Monitoring settings in the top right corner and select Set up agentless or AMP monitoring.
Type in your
Manual injection options
To view all the available manual injection options supported for agentless monitoring:
Select Applications from the navigation menu and then click an application for which the Injection type is Manually Injected (see filters in the left).
Click the Browse button (...) and select Edit.
In Setup, click Agentless Real User Monitoring setup.
Click the drop list under Insert monitoring code. The available manual injection options are the following:
Click Download to download the selected option.
- The above listed features are available for environments that have a minimum OneAgent version of v1.127 and above.
- Install a Cluster ActiveGate.
- Go to Settings > Public endpoints. In the ActiveGate URL text field, type the URL where your new AciveGate can be reached. The URL must be publicly accessible and able to accept HTTPS requests.
Note: By default, Cluster ActiveGate listens on port
9999. If this isn't desired, it's possible to change the port in the ActiveGate configuration file. Alternatively, you can use the port of your choice and then redirect the traffic to port
9999 using firewall settings.
Make your cluster production ready
Load balance multiple ActiveGates
If you take this approach, you'll need to provide your load balancer URL in the activeGate URL text field, as explained above. Requests that your load balancer forwards to Cluster ActiveGates appear as follows:
GET and POST requests for transmitting session information to Dynatrace Managed:
Note: Be sure to configure the load balancer to set the
x-forwarded-for parameter for all forwarded requests. This parameter contains the IP address of the original request. Dynatrace needs this parameter to determine where the request originated from.
Load balancer should terminate SSL as this is very expensive on Cluster ActiveGate. For a higher performance and if security constraints allow it, traffic can be forwarded via plain HTTP from load balancer to Cluster ActiveGate.
CDN or caching proxy should forward all requests to
- Go to Settings > Public endpoints.
To simplify updates and configuration changes, you can use the Dynatrace API to get the current JavaSript tag.
To investigate problems that you may encounter with agentless real user monitoring, confirm the following:
- The response of the beacon endpoint starts with
- The application in the Dynatrace web UI shows data.