Unwanted Helix RUM Script Injected on AEM 6.5 Publish Pages | Community
Skip to main content
N
NandheswaraS_
September 8, 2025
Solved

Unwanted Helix RUM Script Injected on AEM 6.5 Publish Pages

  • September 8, 2025
  • 1 reply
  • 1101 views

Hi Everyone,

 

We are running AEM 6.5 on-premise (AMS) and recently noticed that our Publish pages are automatically including the following script tag:

<script defer="defer" type="text/javascript" src="https://rum.hlx.page/.rum/@adobe/helix-rum-js@%5E2/dist/micro.js" data-routing="p00000-e000000"></script>

 Observations

  • The script is not present in Author mode.

  • It is always injected in Publish output.

  • We confirmed it by hitting the publish instance directly (bypassing dispatcher and CDN) using curl:


This returns the script element, meaning it is injected inside Publish itself.

Analysis

  • The script is not authored in our page templates, HTL, or clientlibs.

  • Searching /apps and /libs in CRX/DE gives no matches for rum.hlx.page or helix-rum-js.

  • This indicates the injection is not content-based, but done by an OSGi bundle or service active only on Publish.

  • From documentation, I found this script is part of Adobe Helix / Edge Delivery Services Operational Telemetry (RUM = Real User Monitoring) used in AEM as a Cloud Service.

  • Since we are on AEM 6.5 on-prem, we do not require this script.

Questions

  1. From which bundle or service is this script injected on AEM 6.5 Publish?

    • Is it part of a Helix/Franklin library shipped in AMS environments?

    • Does anyone know the OSGi config PID that controls it?

  2. What is the recommended way to disable/remove this script on AEM 6.5 Publish?

    • Can we stop/uninstall the responsible bundle?

    • Or override the OSGi config under /apps/<project>/config.publish/?

  3. Are there any implications of removing it on an on-prem 6.5 environment (we believe it’s only telemetry for Edge Delivery)?

Best answer by konstantyn_diachenko

Hi @nandheswaras_ ,

 

I checked the documentation about Cloud Manager for AMS and didn't find screenshots with an env variables console per environment that AEMaaCS has. 

 

Nevertheless, there are Cloud Manager API and Cloud Manager CLI that allow managing of env variables. To be able to set environment variables, you have to to be added to the Deployment Manager role in the Admin Console (https://experienceleague.adobe.com/en/docs/experience-manager-cloud-manager/content/overview/faqs#set-variable ).

 

Check those resources: 

1 reply

konstantyn_diachenko
Community Advisor
konstantyn_diachenkoCommunity Advisor
Community Advisor
September 8, 2025

Hi @nandheswaras_ ,

 

This script is added not on the AEM Publisher node and even not on the Apache/Dispatcher. I guess, it's an extension (filter) on the AEM CDN that adds this script to the HTML response.

 

Below you can find answers on your questions.

 

1. Adobe Experience Manager uses Operational Telemetry to gather operations data that is strictly necessary to discover and fix functional and performance issues on Adobe Experience Manager-powered sites. This service is not bundled in the OSGi environment.

 

2. Adobe Experience Manager as a Cloud Service (outside of Edge Delivery Services) provides environment variables to control Operational Telemetry behavior through Cloud Manager configuration.

To disable Operational Telemetry, set an environment variable in Cloud Manager:

  • Variable name: AEM_OPTEL_DISABLED
  • Value: true

To re-enable Operational Telemetry, remove this environment variable.

Reference: https://www.aem.live/docs/operational-telemetry#disabling-operational-telemetry 

 

3. Adobe recommends maintaining Operational Telemetry for its performance and optimization, allowing Adobe to help improve your digital experiences through insights and data, yet you retain control and command over this feature. The service operates with seamlessness and silence, imposing no burden on website performance. Note that disabling telemetry means forgoing opportunities to identify performance bottlenecks and optimize visitor engagement based on real-world usage patterns.

 

Kostiantyn Diachenko, Community Advisor, Certified Senior AEM Developer, creator of free AEM VLT Tool, maintainer of AEM Tools plugin.
    N
    NandheswaraS_Author
    September 9, 2025

    Hi @konstantyn_diachenko,
    I don't see any options to set the environment variable on the cloud manager, Is there any special permission needed to add the variable?
    My intention is to remove this script from all of my pages, since i'm using the On-perm AEM Managed Services 6.5.22.

    konstantyn_diachenko
    Community Advisor
    konstantyn_diachenkoCommunity AdvisorAccepted solution
    Community Advisor
    September 9, 2025

    Hi @nandheswaras_ ,

     

    I checked the documentation about Cloud Manager for AMS and didn't find screenshots with an env variables console per environment that AEMaaCS has. 

     

    Nevertheless, there are Cloud Manager API and Cloud Manager CLI that allow managing of env variables. To be able to set environment variables, you have to to be added to the Deployment Manager role in the Admin Console (https://experienceleague.adobe.com/en/docs/experience-manager-cloud-manager/content/overview/faqs#set-variable ).

     

    Check those resources: 

    Kostiantyn Diachenko, Community Advisor, Certified Senior AEM Developer, creator of free AEM VLT Tool, maintainer of AEM Tools plugin.
      Terms & ConditionsAccessibility statement

      Loading footer...