Android Application Auto-Instrumentation Steps

Using the Mobile Agent, auto-instrumentation for Android allows anyone to instrument any Android Application Package to be injected (without access to the original source code) and the app to be monitored.

• 
  Activity lifecycle data – performance monitoring of application startup and web transition response times.
  
• 
  Crashes – detection and reporting.
  
• 
  Real user experiences of the flow within the app (e.g. responsiveness on user actions, like a button touch*)).
  
• 
  Web requests – by tagging them.
  
• 
  Web request events (e.g., reporting execution time and identifying third-party requests).
  

• 
  Before doing the following activity, we will have to rebuild the application after inserting the Dynatrace JavaScript ‘init’ code in the index.html in the section as a first script tag.
  

• 
  Copy the /Android/auto-instrumentor/APK-Instr.properties template to /app (location of generated signed APK to be instrumented) and rename it to -APK-Instr.properties. (e.g. app-release-APK-Instr.properties). Make application-specific settings in the copy, not the template.
  
• 
  You must uncomment and change the cpwrUEM_startup.sApplId=Store
  
• 
  You must change the cpwrUEM_startup.agentPath=https://abc.com/xyz
  
• 
  You must uncomment and make the similar cpwrUEM_startup.useAnyCert=true
  
• 
  You must uncomment the cpwrUEM_action.sendEmptyAutoAction=true
  
• 
  You must uncomment the cpwrUEM_logging.level=debug and then save the file.
  

• 
  Run instrument with apk and prop parameters in the command line:
  
• 
  cd /app
  
• 
  /Android/auto-instrumentor/instrument.cmd apk=app-release.apk prop=app-release-APK-Instr.properties.
  
• 
  After successful result you can find the final .apk from the /app//dist/-final.apk location.