For a large customer, we would like to instrument the mobile SDK, and show them additional value, end to end for their critical apps.
We are already using UEM/Real Users and Synthetic transactions.
Now, they use Xamarin "framework" in order to build their apps on a ".Net like" environment.
I have seen a couple of examples for Eclipse, where all you need to do is load the dynaTrace libraries, and use auto-instrumentation.
Is there such a guide for Xamarin? Customer builds the app in Xamarin and then generates the binaries and that's it.
I wonder how to instrument while they are in the building/development process.
Thanks in advance,
Answer by Joseph H. ·
German, If I understand you correctly, you see the http call from the mobile app, but the backend piece of this HTTP call is not showing up in the User Action Purepath.
A few things to check:
1) Are you sure there is a dynatrace agent in the backend which this mobile app is talking to?
2) We add some tokens to the HTTP request, is it possible that the dynatrace tokens are being removed before the HTTP request makes it to an instrumented tier?
3) Do you see the backend purepath in Dynatrace, even if it is not connected to the frontend user action purepath? This step is important, because we must first see the backend purepath before we can start worrying about glueing them together. If the backend purepath does not exist, then we must focus on that issue first before expecting to see it in the User Action Purepath.
Answer by Carlos S. ·
Just an update, I was able to instrument yesterday a mobile app built with Xamarin, since we finally had access to the app from our customer.
Dynatrace server 5.6
ADK version 22.214.171.12480 (below 6.1 seems a little fragile...)
1 out of 10 attempts, I was able to see the mobile visit, and related info, and I believe I received it because the mobile app crashed, and sent over the exception + App name + response time.
API Level - it is KEY!
Now, it is very important to make sure the API target level is 16 or below, for a mobile running Android 4.2 and above.
We built the app again using target API 16, for Android 4.4.2
Basically we can instrument and then install without issues an app built with Xamarin using auto-instrumentation:
C:\Android\Compuware\AutoInstrumentation>instrument.cmd Usage: apkit.bat apk=apk-file prop=instr-property-file keystore=keystore-file-na me storepass=keystore-password alias=keystore-alias
Any thoughts would be appreciated!
Answer by Dominik P. ·
There is a Xamarin Nuget package now available: https://www.nuget.org/packages/Dynatrace.OneAgent...
Answer by Joseph G. ·
Thanks - that makes sense now and you've both clarified using this approach. So it sounds that if I want to be able to understand from the user perspective I should probably run a synthetic test in either Dynatrace or Webpagetest to be able to understand the UX . Ideally I want to know how the pages created render with those metrics and it sounds like another approach is needed?