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

Mobile RUM monitoring with F5 escenario

alejandro_herna
Organizer

We have plans to integrate mobile RUM in our monitoring enviroment and we have a very similar escenario as the scenario 3 in the documentation:



So, we want to install 2 cluster ActiveGates and we have F5 load balancer, what are the considerations and setup needed for this scenario particularly for F5 balancer?

 

4 REPLIES 4

Actually if you have loadbalancer before dynatrace you don't have cluster active gate. This component is usefull when you have multiple dynatrace nodes. Actually the only think which should be important for you is open traffic without cutting out dynatrace header on F5.


I am not sure if i understand you correctly, you will still need the CAG if you want to do Synthetic or Mobile RUM. F5 or not.

There are two options. If you have mobile app API covered by oneagent, you can configure app in dynatrace to pass traffic via endpoint added to your API by OneAgent. In such case you don't have to bother about anything because your API is public available I suppose.

If you don't have such thing or you don't want to configure it that way you have to send traffic from mobile app directly to Dynatrace server. If you have Cluster node that is public available you don't need external CAG because DT cluster has embedded one.

If your Dynatrace cluster isn't exposed public it's recommended to use CAG which will be you public endopint (you can configure it by setting domain and certificate or hide id behind F5). In such case app will send data via CAG to dynatrace cluster.

Sebastian

In last scenario, as I understand it, you can use a LB in front of AGs, to terminate and load balance. Which may be the preferred way, when F5 is available,
Multiple CAGs for redundancy/continuity and capacity purposes,

The original question I thinks has been answered in the mean time in
https://answers.dynatrace.com/spaces/482/dynatrace-open-qa/questions/242036/recommendations-for-conf...