question

Rejith R. avatar image
Rejith R. asked ·

MobileApp Monitoring - Delay in metrics

Android Mobile Monitoring data (User Actions & Web requests) appear in Dynatrace console only after around 10 minutes they have actually made. What could be the reason for this delay ?

mobile monitoringandroid
10 |2000000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

Sebastian K. avatar image
Sebastian K. answered ·

Mobile app is not sending data on the same way as Web application. There data has to be sent almost immediately because you can always close browser. Mobile app has local storage, data are sent in chunks. If somebody is not clicking a lot it may be delay. Another thing is processing collected data by server to present them it takes 1-2 minutes most of the time.

You can use fiddler for monitoring mobile network traffic, check how often data are sent to dynatrace

Sebastian

Share
10 |2000000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

Patrick H. avatar image
Patrick H. answered ·

Mobile agent sends data with a max delay of 120 seconds. During correlation there is a timout of max 150 seconds to link service requests to it - so if the data has webrequests but no service to be linked is found this timeout also hits to ensure al necessary data is already available and we do not miss soemthing (if a service to be linked is found, then processing is faster). In worst case we then already are at 4.5 Minutes. After mobile correlation there still are some other analyzers processing the data. User actions will be visible in UI faster than Session related data, as the Session processing is again a different step. The generation of aggregated Metrics also happens in a scheduled way, so is not recalculated every second which also introduces some delay. Also the data needs to be stored to Cassandra/elasticsearch to be available across all cluster nodes.

Hope this sheds a bit more light on it.

Share
10 |2000000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

Rejith R. avatar image
Rejith R. answered ·

@Sebastian K. Is there a way to control the size or any other parameter of this "local storage" ? Our instrumented app is not yet in production and not heavily used. But we would like to get the metrics quicker than what we are receiving currently

1 comment Share
10 |2000000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

No, the send interval cannot be adjusted (but data is also flushed instantly when the app is backgrounded or terminated). See my Answer for a more detailed analysis of what happens.
There is the option do manually flush all finished agent measurements, but this is not recommended as it will only increase communication overhead won't really have a noticable speed impact on when you see the data on the cluster for the reasons described in my answer.

0 Likes 0 · ·

Space Topics

mobile monitoring dotnet synthetic monitoring reports iis chat kubernetes servicenow amazon web services mysql mainframe rest api errors cassandra dashboard oneagent sdk cmc application monitoring openkit smartscape request attributes monitoring developer community user tagging log monitoring services ufo syntheticadvisory activegate ip addresses auto-detection high five award oracle hyperion webserver uem usql iib test automation license web performance monitoring ios news migration management zones index ibm mq web services custom event alerts notifications sso host monitoring knowledge sharing reports browser monitors java hybris sap vmware maintenance window user action naming javascript appmon ai synthetic classic availability tipstricks automation extensions diagnostic tools session replay permissions davis assistant faq documentation problem detection http monitors server easytravel apdex aws-quickstart network docker tags and metadata cloud foundry google cloud platform synthetic monitoring process groups account usability dynatrace saas gui paas openshift key user actions administration user actions postgresql synthetic locations oneagent security Dynatrace Managed user management custom python technologies mongodb openstack user session monitoring continuous delivery citrix configuration alerting NGINX timestamp action naming linux nam installation masking error reporting database mission control jmeter recorder apache mobileapp RUM php threshold azure purepath davis scripting agent aix nodejs android