topic Re: How to disable Real User Monitoring on Apache? in Real User Monitoring

How to disable Real User Monitoring on Apache?

shashank_b_agra — Wed, 08 Oct 2025 08:37:27 GMT

Hi, I need to install Dynatrace on my Apache server, but I would need the RUM to be turned off from the beginning. I just need the API response time, and I don't want to be bothered with RUM.

The thing is, I will be doing it on the Production server and don't want it to break anything.

Is it possible to do that?

Re: How to disable Real User Monitoring on Apache?

alonso_decosio — Mon, 20 Jan 2020 16:15:38 GMT

There’s a couple of ways that you can do that:

1) Define the application and disable RUM for it: Application > Select the new applications > edit > disable Real User Monitoring

2) Disable the JS injection on the process group: technologies > select de process group > edit > disable JS injection ( if you have more that one instance of Apache on that process group, this will afect all of them).

Re: How to disable Real User Monitoring on Apache?

shashank_b_agra — Mon, 20 Jan 2020 16:25:16 GMT

@Alonso - Thanks Alonso for your response. Is there a way to do it from the server?

I mean I am installing it by using the following instructions by extracting the zip file of Dynatrace on apache server -

I mean is there a way to do it via configuration or by enabling/disabling any tag in the configuration?

https://www.dynatrace.com/support/help/technology-support/operating-systems/solaris/installation/install-oneagent-on-solaris/#installation

Re: How to disable Real User Monitoring on Apache?

skrystosik — Mon, 20 Jan 2020 18:22:03 GMT

It's not possible in that way, but you can just disable default user application in dynatrace. In such case, RUM will work only for those that were already configured.

Sebastian

Re: How to disable Real User Monitoring on Apache?

Julius_Loman — Tue, 21 Jan 2020 07:34:18 GMT

Based on my experience it is almost always safer to disable the RUM injection at the process group level. In that case, the RUM code does not get executed in the agent at all.

If you just define an application and disable real user monitoring for the application, the RUM code in the agent will still be active. If for any reason someone accesses web application that is not disabled via this apache http server, the RUM injection will happen.

Re: How to disable Real User Monitoring on Apache?

skrystosik — Tue, 21 Jan 2020 08:30:12 GMT

You're right but if this process group does not exist, you will not be able to do it before agent installation.

Sebastian

Re: How to disable Real User Monitoring on Apache?

Julius_Loman — Tue, 21 Jan 2020 09:47:21 GMT

Actually the Apache restart time matters. Process groups are discovered immediately after OneAgent installation. So you can disable it on the process group level just after OneAgent installation and before Apache server restart. That is probably the safest practice.

Re: How to disable Real User Monitoring on Apache?

skrystosik — Tue, 21 Jan 2020 10:02:35 GMT

You're right 🙂

Re: How to disable Real User Monitoring on Apache?

PatG — Tue, 23 Sep 2025 15:55:03 GMT

Anyway to disable on just one of the VirtualHosts in for a single instance of Apache httpd?

Re: How to disable Real User Monitoring on Apache?

Julius_Loman — Wed, 24 Sep 2025 06:40:22 GMT

You need to define a web application with detection rules for the particular virtualhost and disable RUM on that virtual host. Also, make sure the web app detection rule is on the top. There is no alternative if you need RUM enabled on other hosts within the same Apache httpd process.