This website uses Cookies. Click Accept to agree to our website's cookie use as described in our Privacy Policy. Click Preferences to customize your cookie settings.
Accept
Reject
Preferences
FAQ
Troubleshooting
Articles about how to solve the most common problems
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 
New Article

Using RUM manual insertion for an application set up for automatic injection

Aaron_Schultz
Dynatrace Contributor
Dynatrace Contributor

on ‎29 Jul 2026 07:20 AM - edited on ‎29 Jul 2026 01:35 PM by Dynatrace Guru

Summary

For your RUM application, it may be necessary to switch from automatic injection to manual insertion or simply use both methods. This article should guide you through the changes necessary for a successful transition and to troubleshoot any errors that may occur.

Problem

When using the manual insertion method for RUM, you may encounter issues like missing RUM data. Some issues may be related to the failure of the JS request or the beacon request. Some problems you may see are:

  • Missing RUM data.
  • HTTP 404 responses on the JS requests.
  • HTTP 404/501/503 responses on the beacon request.

Troubleshooting steps

Here are a few symptoms that indicate whether the transition to manual injection is causing the issue:

  1. If the transition isn't configured correctly, you'll start losing RUM data. Please check that you’re still getting RUM data in Dynatrace.
  2. If you’re not getting RUM data, check your application with Chrome dev tools for any issues.

Issues with JS request

First, check if the JS injection is working correctly by opening the Chrome developer tools on your application and searching for a request ending in _complete.js (the beginning of the filename will vary).

image.png

  1. If the request is failing, please check if the request URL should start with https://js-cdn.dynatrace.com
  2. If the request URL looks correct but you're still getting an error, please check your firewall rules and that your application can access the public internet
  3. If everything above is correct, please open a case with a HAR file attached containing the replicated issue.

Issues with request beacons

  1. If the JS request is successful, next,  check the beacon request to see if the data is returning to Dynatrace.
  2. To view the beacon data, open up the Chrome development tools and search for rb_ OR bf_
  3. Check if the beacon has a status other than 200.

Example of a successful request beacon

image2.png

 

  1. If your beacon returns with a HTTP status code such as 503 or 404, this is a configuration issue, and continue to proceed to the Resolution below.
  2. If the beacon's response does not start with OK, please check your firewall rules or how your application may handle URL routing.

An example of a successful request beacon payload

image3.png

Resolution

If the OneAgent is still installed on the process group that serves the web application (automatic injection may still work).

  1. Select your method of manual insertion from the manual insertion page. For example, let's use the JavaScript tag option.
  2. Copy the JS tag and add it directly to your code.
  3. Then everything should continue to work as before.

If OneAgent is not installed on the process group that serves the web application (automatic injection no an option).

  1. First, you’ll need to ensure your application is accessible from the external internet.
  2. Then, in the application's settings in Dynatrace under General settings —> Beacon endpoint
  3. Change the beacon endpoint from Default settings to Cluster ActiveGate
    1. If you’re using Dynatrace Saas, Dynatrace handles the Cluster ActiveGate. Nothing further is required.
    2. If you’re Dynatrace Managed, you’ll also need to create a Cluster ActiveGate if you haven’t already done so.
  4. Finally, from the manual insertion page, select your method of manual insertion. For example, let's use the JavaScript tag option.
  5. Copy the JS tag and add it directly to your code.
  6. Your RUM data should now report as expected.

Note: You may not see changes for the updated Cluster ActiveGate configuration for up to 1 hour, as there is a 1-hour caching for the manual insertion JS agent to accept the new configurations.

What's next

  1. Opening a support case — If the article was not able to help you resolve your issue, please open a support case for further assistance. In the support case, please provide:
    • A link to the application in Dynatrace
    • If the application itself is public, a link to the page you’re having issues with.
    • A har file with the issue replicated.
      • Make sure that you can see both the JS request and the beacon request
    • Inform which method of manual insertion you’re trying to use. (JS, inline, code)
    • Steps that you have taken so far.

Version history
Last update:
‎29 Jul 2026 01:35 PM
Updated by:
Dynatrace Guru