Mobile App Monitoring retries limitation

[monique_vanwall]

we have a number of mobile apps that are monitored by Dynatrace.  Due to migration from Managed to SAAS we had to reconfigure the config of the apps.

Helas, not all applications were adapted , so some of them still have the config for managed.  On netwerk we see a very high load comming from these applications, we believe this is due to a high number of retries.  (we see a steep increase on the number of calls)

And now my question : is there a config in DT managed that determines how many time a retry is done ?  Because of network team complaining on the very high load.

[Patrick_H]

This needs more details for an in-depth answer, but I'll try with what I know from that information.

Short answer: No, there is no retry configuration that can be changed.

More elaborate answer - the retry amount depends on what was changed in configuration or infrastructure:

• if the beacon endpoint (AG, OneAgent) was shut down, the agent does 3 connection tries and then shuts down
• if the application was deleted or capture was disable and the beacon endpoint is still available to answer the request, the agent stops after this one request and tries again on restart or after 2h

Which change exactly was made to the configuration/infrastructure setup? - (old) App releases configured for Managed will still try to reach the managed beacon endpoint and new Apps configured for SaaS will try to reach the SaaS beacon endpoint. If the backend is monitored by OneAgents then end to end linking of web requests for mobile apps will only work for the mobile app on same Cluster where the OneAgent reports to (Managed or SaaS)
So on a migration it is not expected to have a steep increase of beacon requests.