We recently instrumented an Hybrid Application with the Auto-Instrumentation method. The application technology is IBM MFP which is based on IONIC. The
network library being used by the mobile application is Angularjs $http service.
The Instrumentation was done without any noticeable issues but we are not able to see any UEM visit from mobile application request for the MFP application although the PurePaths are collecting and their entry point is 'Web Request'.
The only thing I would like to say that our appmon/agents are version 6.5.x but the bootstrap version is 6.2.x for agents. We are not sure whether this could be the reason to said problem or something else.
Edit: Adding one more observation that while testing we found that all our actions from the mobile application dropped/skipped.
Edit: The dropped/skipped User Actions has been resolved after using the Mobile Agent ADK version 126.96.36.1995 but the mobile requests are not stitching to the application server.
Did anyone already instrumented the IBM MFP on top of IONIC application?
Any suggestions to resolve this issue will be highly appreciable, thanks.
Solved! Go to Solution.
It seems for the ADK agent the dtcokie and dtadktag are not being transferred on web headers till app layer. Try enabling web request headers capturing in DT and check. Note, try not to send the data inside the Adapter fields, but in web request headers.
Also, try loading the hardcoded (local) bootstrap agent inside apk and keeping the version of ADK agents and DT coherent, to see if it works.
Thank you for your reply. Till now we did with the coherent ADK and also with the lower ADK but in both cases no success.
We also enabled the Web Request and verified that the dtcokie and dtadktag are present in the header field at application layer.
dtAdk=3437356811_9_TestMobile_m; dtAdkTag=MT2_0_0_TestMobile_0_0_0; dtCookie=3437356811_1|Uk9MfDE
Now one more try we are going to do and that is simple upgrade from 6.5.11.xxxx to 6.5.13.xxxx to further investigation.
Hi Babar, I can suggest to check if you are sending the data to correct Domain, as mentioned in the Advanced configuration.
Also try to keep the environment versions updated. If these doesn't help, try opening support case. (+Curious to know, if are you able to get "named user actions" or just plain Web Requests in visits with auto instrumentation?)
Hello @Rajesh S.
Apologize for the late update to this post.
Problem was resolved after long R&D and taking following measures: