How to disable Real User Monitoring on Apache?

[shashank_b_agra]

Hi, I need to install Dynatrace on my Apache server but i would need the RUM turned off from the beginning. I just need the API response time and does not bother about RUM.

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

Is it possible to do that?

[alonso_decosio · Accepted solution]

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).

[shashank_b_agra]

@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/ins...

[skrystosik]

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

[Julius_Loman]

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.

[skrystosik]

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

Sebastian

[Julius_Loman]

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.

[skrystosik]

You're right 🙂