Showing results for 
Show  only  | Search instead for 
Did you mean: 

Turn off rum per application

DynaMight Champion
DynaMight Champion


When turning off RUM on a application, this means that all agent's have to filter on incoming request's and decide to inject or not?

In other words is it not much more efficient to turn RUM off on PG's?

KR Henk


Well, the rule of RUM on the agent side is based on the rules created for that application (URL or any other option) So I would assume that the Agent would need to check it out.

On the other hand, you can shutdown RUM in PG. For us, is more efficient that way. If the PG is serving multiple application endpoints (an apache with multiple sites?) you just shut down at the PG level and it's done. (It would set alarms if you have enabled the spike/drop option at the anomaly of the app) .

Services Solution Engineer @PowerCloud - Observability/CloudOps Certified / Former SE @Dynatrace.

DynaMight Legend
DynaMight Legend

As @Dante P. writes, turning on RUM at the process level is much more effective and applies in all cases. If you encounter misbehaviour with RUM on, you should definitely disable it on process group level.

If you turn RUM off for one application in Dynatrace, the RUM code still runs and decides just by the application rules if to inject or not. That means for example if a user accesses the application by another URL (for example directly by the IP address) and you don't have that URL match for your disabled application, the RUMw would still inject as it is another application.

Certified Dynatrace Master | Alanata a.s., Slovakia, Dynatrace Master Partner

Featured Posts