Solved! Go to Solution.
Hi, I have setup Dynatrace auto-instrumentation on an Android mobile app. I can see some limited button presses and few network connections have been made in the mobile app. But it doesn't show complete user actions(button clicks) or all the network connections app makes.
Below is what I have in the main build.gradle file.
Do I need to add anything else in the config to enable full capture of button clicks and network calls?
apply plugin: 'com.dynatrace.instrumentation'
@Shamila it depends on how your application is written, especially what UI toolkit are you using. For android auto-instrumentation of JetPack Compose is not (yet) supported. Also when it comes to network requests, they are likely captured, but not bound to user actions. Be sure to check the network tabs. If that's not your case, check if you are using supported library for auto-instrumentation here.
Thanks. This android app uses standard Android buttons. It doesn't use JetPack Compose.
The problem is, it does sometimes record button and lifecycle actions. However, Dynatrace is not capturing all the button clicks/lifecycle changes.
Same with the network calls. Some calls are recorded but not all of them. HttpURLConnection is being used to make web requests, and it is supported by Dynatrace auto-instrumentation. But Dynatrace is not capturing all the web requests.
What does app need to do extra in the below config (the screen shot attached) to capture every button click, every life cycle changes and every web requests when app does auto-instrumentation? Is it missing anything in the below configs?
Please advise. Thanks.
@Shamila based on your screenshot everything seems fine. so nothing to add there in the first place.
there might be several reasons for your user actions and/or web requests not to be automatically tracked by our agent.
Some examples are part of this FAQ: https://www.dynatrace.com/support/help/how-to-use-dynatrace/real-user-monitoring/setup-and-configura...
Here you can find some info on sensors we are using to detect user actions: https://www.dynatrace.com/support/help/how-to-use-dynatrace/real-user-monitoring/setup-and-configura...
Hence there are also cases, which are not covered by auto-instrumentation.
Therefore, you can of course always use manual instrumentation (using OneAgent SDK for Android) in addition to auto-instrumentation to track specific user actions / define their labels etc. - some info here:
Hope this helps... if you require us to take a closer look into this and help out it's best to have a support ticket created.