on 22 Jan 2024 07:00 AM - edited on 09 May 2024 05:26 PM by HannahM
If you've encountered an issue related to mobile application monitoring, first ensure the following:
Your technology is supported by Dynatrace. See Technology support | Mobile app Real User Monitoring.
You're using the supported version of the OneAgent SDK or Dynatrace Android Gradle plugin. See the table under How long are versions supported following rollout?.
The issue that you're experiencing is not related to any of the currently known limitations. Check one of the following pages:
You've enabled logging and checked the logs to see what went wrong. See the information below on debug logging for the following technologies and operating systems. You might also need to provide the logs if you decide to contact Dynatrace Support.
The other monitoring tools that you use are compatible with Dynatrace. See the related information for Android or iOS.
To troubleshoot specific issues, check one of the sections below.
You might have to adjust the application or server infrastructure to allow OneAgent to reach Dynatrace. Explore Adjust communication with OneAgent SDK for Android or OneAgent for iOS advanced configuration for more information.
The following list contains some problems that you might experience.
applicationId
and beaconUrl
. These are provided in the mobile instrumentation wizard for Android or iOS in Dynatrace.
Info.plist
file.Check if Dynatrace is reachable from within your company network.
You might have missed one of the configuration steps described in Instrument hybrid apps.
OneAgent truncates such reported values when they exceed 250 characters.
Dynatrace automatically instruments most web requests. However, you have to manually instrument web requests in certain cases. Check the information on web request monitoring for OneAgent SDK for Android, Dynatrace Android Gradle plugin, or OneAgent SDK for iOS.
For the Dynatrace Android Gradle plugin, web requests might be missing when you use the Firebase plugin.
OneAgent only attaches web requests to a user action triggered within a specific timeframe. The timeframe starts when the action opens and ends 500
ms after the action closes. You can change this value with the timeout
property for Android or with the DTXAutoActionTimeoutMilliseconds
configuration key for iOS.
To construct user action names, OneAgent captures the control title from different attributes/fields, so make sure that you pass the correct values to these attributes/fields. For details, see the information on user action naming for Android, iOS, or our React Native plugin.
You can also define user action naming rules to change the automatically generated names to a predefined name. See Create custom user action names for mobile applications.
For issues specific to your technology or operating system, check one of the following pages:
If you can't resolve an issue with your mobile application, please contact a Dynatrace product expert via live chat within your Dynatrace environment.