Mobile App Health: Splunk AppDynamics Mobile Real User Monitoring

Today's session, I would like to introduce myself. I am Adita Kumar. I am customer success specialist working out of Singapore and.00:09I look after for all the post sales customer enablement adoption and all. So I am part of customer success team APJC. So today we are here to discuss about.00:20You know, one of the key feature or the use case in appdynamics. So today we are we'll be talking about AppDynamics mobile real user monitoring. Okay, so today's agenda would be, you know, we'll be discussing some of the basic.00:32About user monitoring, what are the use cases, how we can instrument and set up, what are the key metrics and KPI, then, you know, once we are done with the, you know, slides deck and then we'll go directly to our, you know, internal demo controller to, for a demo purpose and to see.00:50For different metrics and, you know, data which appd is able to bring out of mobile applications. And then we are open for taking any questions and all.01:10So the goal of this session is to provide an understanding of mobile real user monitoring capability in Splunk and we will review some of the common use cases and capability in our demo controller. All right, so we'll start with the.01:22With the mobile real user monitoring, and before that also we can start with the end user monitoring 1st of all. Okay, so I I'm hoping that everyone who has joined the call, they are, you know, pretty much aware about what AppDynamics does, why, what are different use cases and telemetry appd help.01:40Any customer or business application to bring out. So two major component which appd will help customer to, you know, monitor their application is application performance monitoring and end user experience monitoring. So application performance monitoring is predominantly.01:59We are talking about all the backend services or the application code which we will be onboarding through our various kind of app agent like java.net PHP or.02:19You know js and you know I mean, it it just gives us how our backend services or business services are functioning right now. And if there is any performant bottleneck or issues then appd will be able to track it down and help you to resolve it, you know, proactively. But that is not the.02:31The only thing which suffice or guarantee your application performance because NO matter how good your business services would be functioning, there is other way of looking at because the application is being delivered digitally to the, to the users who whoever is supposed to consume that application and the.02:51Mode of consuming that application is predominantly either through browser or their mobile devices.03:12So just to look at end user perspective and how they are consuming your application, is that application is loading in their browser correctly and the pages are, you know, loading perfectly in their browser and how many users are interacting with your application? What is their device type? What is their.03:18Browser, what is their location, and if it is a global application, then we will be more concerned about the application availability from the different part of the geo, right? So just to get the real user data in your.03:38Along with your backend service makes it, you know, more comprehensive and and helpful to troubleshoot. Let's assume one scenario where you are troubleshooting your back end service, but if you have to, you know, double it down your, you know, user data, let's say some of the users are complaining that they are not able to, you know.03:52Functioning with your application or the application is not being loaded to their, you know, or or it is not available to their region, then unless you have the, you know, end user monitoring, then we won't be getting full picture out of it, right? And with the use of real user monitoring, we can actually go and drill down to the session.04:13Level data also, right? We can specifically go into a particular user session or a group of session and start analyzing that if the particular user has got getting impacted, that what are the activity that particular user is doing within their session and what all the backend services are.04:33Invoking and if that session is being, you know, running for so long, then what are the, you know, root cause beneath it? And if it is related to any backend service, then all the data will correlate it automatically. So once you onboard backend plus real user monitoring, then you don't have to tie the data together or.04:52Manually appd does it automatically, right? You just have to onboard the backend as well as the front end service on the same application. Then the, you know, the data will be seamlessly correlated within Abdi.05:12So these are the you know we have talked about what is the mobile real user monitoring, how Mrim fits into end to end observability and difference between browser real user monitoring and mobile real user monitoring is that.05:26Okay, so browser real user monitoring, we are specifically targeting to the user who are coming through web browser and for mobile real user monitoring we are targeting to the user who are connecting to the mobile application. Okay, so this is one of the dashboard, ok, where we are.05:42Checking mobile application performance though we will be going to the demo controller to look at and and discuss about, you know, the metrics which is coming on a home homepage. And this is predominantly on a home dashboard for any mobile.06:01Application which we are onboarding as you can see that we are currently monitoring one of the demo application which is giving us some different HTTP error error metrics, cache metric crash metrics, HTTP error distribution, what are the load time, what are the requests, whether it is healthy.06:17Normal slow, very slow.06:37All of that metrics you will be getting and then further those, you know, KPI are getting, you know, bifurcated based upon what mobile careers users are using, what are the application version they are using, what are the mobile devices they are using, right? So there are different category of, you know, metrics which.06:39Our agent is, you know, sending to appdynamics. So we are getting performance for your network request. Network request is nothing but your front end pages in a simpler term. And apart from that, we are getting mobile application crash.07:00Matrix also ok so before it actually interacts through the backend service, there are, there could be scenario that user are launching their mobile application and it is crashing to their mobile devices by any reason, right? So our agent is able to capture all of them and then we are getting session related data.07:16I mean network request is just a simple, you know, front end page performance, but if if I have to just look the user related session related data, so appd is able to, you know, correlate all the activity which a user would be doing in your application within a session. Session is typically we consider as a.07:36You know, once the users start using an application until it is it is, you know, he's logging out or mobile application is being closed, right? So whatever activity they might be doing within that timestamp, all will be correlated and and you know identified as the.07:56User session.08:16So let's go drill down. Now we'll talk about quickly how we can integrate app dynamics in mobile application and what are the different configuration options. So I'll just, you know, minimize my slides and then go to the demo controller. So let's go and check out on the demo.08:17Controller, how we can do that.08:37So for the today's demo purpose I'll be using two demo controller and the reason for that is different level of, you know, permission. Okay, this demo one controller I am not, you know, admin users so I won't be able to showcase you all the instrumentation and configuration option for that reason.08:40I'm using other controller and rest all, you know, use case discussion and the data which Abdi is able to bring it up. So we'll be using demo one controller.09:00Going forward. And while the controller is getting loaded, if you guys have any question, then please feel free to raise it Yeah so as you can see this, we are on our demo controller.09:11If I go to the user experience, ok, in the user experience, you can see there are browser apps, mobile apps, connected device and all. So we'll directly go to the mobile apps. Okay, so these are some of the mobile application which we have currently onboarded.09:31Okay, so we have some Android application iOS also, ok, so if I click onto the add app and I need to choose the platform, ok, whether I want to onboard Android application, iOS application or this is the cloud cross platform. So cross cross platform is nothing but a s in a single code base for deploying.09:47Your application to Android as well as iOS.10:07Right, so I'll choose here for android. Just for our demo purpose, you can use how you wanted to install the agent. Let's say if I say manual, ok, so these are the, you know, steps which you need to perform. These are the prerequisites which you can 1st of all verify in order to.10:10Instrument the application and then you need to create a mobile app group. Mobile app group is nothing but a, you know, identification of a mobile application in AppDynamics. This is not your application side configuration. This is appdynamics side of configuration, right? So let's say if I say order.10:30To Generate something and then continue, right? So it will, it will create an application.10:50Okay, then these are the let's let it 1st create enabling, so it is now generating the key, right? So this is basically a build.gradle file, ok, which you need to modify, ok? And then you know you.11:00You need to modify your module level build.gradle file and once your mobile SDK will be generated, then you can push the SDK to your play store, and as long as soon as user will be downloading the, you know, mobile updates mobile application update, the agent will be sitting on their mobile.11:20Devices and after that once they will be using mobile application, so you'll start getting the data, ok? So now I'll go to the other.11:40Browser, the controller, if I go to the mobile apps, ok, if I use AD commerce android, ok, so you could see this is one of the Android application which we have instrument like I have discussed it now and the different I.11:51I mean the configuration option which we talk about is the major one is the application key, right? What is your app key? App key is basically identification in the appdynamics, right? For your application.12:10Or so this will be the app key will be used by agent to determine which application the data should be sending right to controller. Now if I go there, so you can see this is an overview, this is the main page of your mobile application monitoring I'm seeing the data for last 1 h.12:22Okay.12:42In that I can see if there is any health rule violation is happening or not, what is the health for my mobile application, any network request which is breaching health rule, what are the crashes? Okay, so how many number of app open per minute? Like in last 1 min, how many times.12:42When my application is getting opened for the user devices, right? What are the number of requests of the.13:02Application is coming, correct? So these are the crash metrics, like what is the crash percentage? What are the number of crashes in your mobile application and what are the HTTP error metrics? If I choose to increase the time, let's say, I'm choosing one.13:11One week, right? So in one week, the crash matrix is 5.8 %. What are the number of crashes is there 3.11 K are the crashes. These are the HTTP and network request in your mobile application.13:28And then you get this like what is your network request health, right? Whether it is slow, very slow stalled or what, and this is a network request time trend. I mean on an average, how much time your network request started taking to.13:44You know, function for the user mobile, right? And these are the top unique crashes for your application. The number of crashes are getting, you know, grouped and categorized under different crash category, and we'll just skip this, this one because this data.14:00Probably will be coming from the thousand days, right? So we are not going to touch base on that. And these are the network request time distribution, the out of the this trend, they are just, you know, distributing that, that what is the 99th percentile of your, you know, network request time. So that means, you know, 90.14:189 % of the requests are, are completing within this.14:39Timeline, nine 9055 milliseconds and only 1 % of the requests which are going beyond that, right? And the crash by devices, we are just now grouping all the crashes according to the device, whether they are coming from the Motorola one plus Google or.14:43What kind of mobile devices, then this, these are very handy, you know, metrics which we are showcasing right now on the dashboard. So the number of app open, which we were showing it here, right? So these are the total.15:00How many number of apps are open, right? Now we are segregating them based upon the location. I mean, how many requests are coming from which part of the world, right? If your application is geographical distributed application.15:18So you can see that application is being loaded 9834 times from the US and if I look at from the India, then it is loading by 3700 202I can drill down it and then we can specifically go to the request, what kind of request it is coming.15:33Same way the end user response time is also being, you know, distributed that which location is taking how much time to, you know, load the application. If I go here, so.15:53So these are the, I mean these are the requests not not not time actually, sorry. So these are the end user requests so from India 12000 nearly requests are coming to our mobile devices, right? And this is the time basically how much time it is taking. So in India it is taking 292 milliseconds.16:05Or, you know, loading the mobile application.16:26Pages. What are the application versions they are using? Okay so some of the user they are using two point oh some of them they are using 2.1. These are the mobile carriers which requests are coming. They're coming from Vodafone, ATT KPN and all mobile devices, what mobile devices.16:30Should they are using.16:50What are the connection type OS version, device memory, device storage, and device battery capacity, right? So if I go directly to the geo dashboard, so everything which we have seen, there'll be, you know, this dashboard is specifically for the geolocation. Here we have every.16:53Thing in place and whatever are the major KPI along with the geo along with the crashes, everything on the main dashboard. Now if you if we have to go specifically looking for a certain metrics for the category, so if I, if I have to specifically looking at the, on a geo geographical location perspective.17:12Then I'll go to the geo dashboard. Then everything which is coming over here, it is again, you know, the crashes are being categorized into the country, from which country, how much percentage application are being crashed, total number of app again according to the country, ok, and these are the location like.17:32Like from US how many times this application is being opened, what are the crash rate and all, I mean, all the KPI are now being, you know, transformed and categorized based upon the location, ok? You could see that these are the major KPI, now we are looking at the only US data, right? If I click it, then it will.17:52Just, you know, hover and then showing the data only for US ok? So, yeah. So this this we have covered. Any question so far before I proceed for the, you know, other use cases? No questions so far, I think you can go ahead.18:12Alright Kevin, NO problem. Okay, so as I mentioned, so we will be touching base on, you know, three major or predominant use case, which we will be looking how mobile real user monitoring data brings bring in and and common.18:32Implement the application performance data and increase the I I would say the view for a user to troubleshoot, right? So as I mentioned, these are the network requests which is your application pages.18:51So this is a login page, this is add to cart. Let me just increase a bit. I could not see the proper name. If you hover, then it will come over here, right? So this is the add to cart age.19:06And yeah. So this is a login page and this is a checkout page basically, right? So, and the crash tab will have all the crashes which are happening in your application. Okay, so total number of crashes.19:21These are 1849 impacted user are 961. You can go directly and see what.19:41Users are getting impacted and what sessions are getting impacted. The total unique crashes means that different category of crashes, right? So these 1849 are being, you know, categorized into three different crash category. What are the overall crash rate in your application right now? And again these.19:47These are the different categories, right? Three, if I go directly and go into the detail.20:07Then it will tell me what, what are the, you know, why this crash is happening and what does that mean? That utilized.crash.mean? Where exactly that crash is being, you know, occurring, and I can go directly to the session and crash distribution again. Okay.20:12Let's close this one and directly you can go to analyze also to see what crash you wanted to, you know, analyze, you can click on that and go into the detail. Then you will get all the details again the same thing but different way of looking.20:29Okay, so the 3rd thing will be the user session, right? So as I mentioned, network request is an individual network page or the mobile page request, right? But if I have to analyze a particular user activity in my application and let's say somebody complains.20:47In that they are not able to.21:07Perform it or they are not able to interact with an application. And if I have to go to user level data, then the best way of looking their, you know, session. Okay, within the session you will get to know what activity they are doing and if at all there is any degradation or any error or perform.21:09When the issue is happening, then we'll be able to exactly pinpoint where the problem start occurring and what are the root cause and root cause. And the root cause could be either crash or a network request performance or it could be any backend service which are getting slow and it is eventually, you know, making the user experience as.21:28You know very slow. So I, I have some of the, you know, sessions and other use cases I would like to, you know, start demoing.21:49Okay, so before that we can look back onto the these metrics and API what are the metrics we can monitor through network this mobile user monitoring, as we discussed about that we can do network request performance crash reporting and diagnostic.22:00User sessions we can.22:20Troubleshoot, then we can troubleshoot the slow and failing user interaction, right? And the crashes would also be linking to the user sessions, ok? Then how the backend is getting correlated to the end user request or the user sessions, right?22:22So let's go and, you know, see the exact use case. I have copied some of the URL which for the demo purpose. Just give me a minute. So 1st we'll be looking the session session related data, right?22:42Okay, let's close all of them, right? Otherwise it will get confused sorry this these are the network.23:02Request based performance, right? So we are into the AD commerce iOS application.23:22Okay, and we are seeing the data for last monday, as you could see and we are under one of the network request performance which is checkout. Check out is our application page basically I would say, and you can see what are the request time and all. Okay, so we are not getting into the detail. Okay, we will just simply.23:28See, ok, what are the.23:48You know, you see this related business transaction, right? So this front end is getting correlated to the backend service, this checkout mobile, right? And I could see that this particular business transaction is currently affecting and there is some performance issue which is going on and that's why this overall.23:50It is making overall user experiences, you know, impacted. So I'll directly go to this checkout mobile business transaction to see why this business transaction is currently seeing the error.24:08I'll click directly to the business transaction and you could see there is some red, ok, so, so we'll directly go to the snapshot and a snapshot is a diagnostic data where you can see what is happening with this business transaction, where it is failing and what sort of, you know, error it is throwing. So we'll go.24:23Directly to the.24:43Eroneous snapshot. We are not taking any normal snapshot. So we are taking erroneous snapshot. Let's take and go into the detail. You could see that user experience is very slow for this business transaction and what are the major contributing factors this particular service, right? Which is e commerce.24:45Service. Everything else is looking ok.25:05The only thing which is impacting seems like this is the one. Okay, so this is a overview, right? These are the potential issues. Okay, so it is just segregating all those potential issues which might or might not be the contributing factor for this overall.25:08User experience impact, right? So you could see there is some JDBC call which is going through from e commerce service to the, this database, right? So you can see what is the problem, right? So this select query is taking 9 s, right?25:26So this is one of the major contributor, right? If you can see the maximum amount of time, this select query is taking, right? So I can go further drill down and talk to my DBA and the database team that why this selective statement is taking so much time and they will help me to either optimize this query or.25:44To identify the issue, right? And once it is sorted, then I can go.26:04Again looking at the other things also, right? So there is some this they are executing some query on the pool. This is another service which it is consuming. Okay, so why this is taking 9 s? So one by one I need to take.26:08All of this into consideration and then once I'll discuss with my developer and the team who is responsible.26:28And owning this platform, then, you know, we'll be able to troubleshoot this and and fix it, ok? And these are the service, right? Demo lab.dot net.com, right? So these are the HTTP calls which are slow. Now this, this.26:36Slow HTTP call could be either in your premise, ok? I mean it could be remote service or the one which you are onboarding. If I directly go and click on drill down into call graph, then you can see right where this is the call graph, right? It will just tell you where this HTTP call is being happened. So if you.26:52You click on that.27:12So this is the call, right? So which is taking 08:30 milliseconds. So now coming back, this is one of the way of looking and user data, right? So now we are not talking about the session. We are just simply talking about the front end page performance of our mobile application. We just have to look the, the network.27:13Request performance and wherever we are seeing any network error or HTTP error or something, then it probably may or may not be, you know, related to the backend service. In our case, we are looking for a specific use case where the underlying problem is the business transaction performance, not the crashes, not the.27:33Any other factor, right? Now we will check for other use case.27:53Just give me a minute ok so this we have done already. Just think.27:58Check all this we have seen already. There was one more which is having crashes. Which.28:31Okay.28:39Let it load my checkout, check out yeah this is one of the other use case, right? So we have this checkout network request. Okay, so user experience is slow.28:43And this is request time, received time and all. Okay, this is the business transaction, right? This is a checkout business transaction and it is actually telling you what are the snapshot, ok, related to this particular network request. This is.28:59The power of appdynamics, it is correlating each and every data, right? So rather than I going directly to the business transaction then sorting out and then start, you know, troubleshooting the business transaction, I can directly go and open this snapshot from here itself.29:14Let it, ok? So now you can see why this is very slow. Again, these are the potential issues, ok? If you go directly slow calls and error, it will list down all those slow method and all. So these are the slow method. You can sort them out with the total execution time.29:32And then start, you know, troubleshooting one by one. And in error, it will list down all those errors if there is any.29:52Now I take other example, just give me a minute. There was one more which is which was related to cash crashes your application yeah.30:04Maybe I down a couple of times. Yeah.30:20If I don't find it, then I'll directly go to the crash, NO problem this is same. Let me go here.30:40This is a session session with Okay let me do this one.31:01No problem, we'll go directly to the crashes. Okay, so let me go to the user experience.31:26User experience, ok. Let's go to the user experience and then I'll open application AD e commerce mobile apps, and I'll go directly to the AD commerce android, right? I'll go directly to the crashes, right?31:34So let's go inside a null pointer, just crash me, right? Go into the details. So if I go to the crash distribution, so these are the devices, these are the OS version and all, ok. So I'll go directly to the.31:51Find all sessions. If I go to the sessions, so it will list down all the sessions which are getting impacted with this crash. And I'll pointed out exception. So I can open any of the session, go and view detail, then in the session you'll get to know what user was doing. These are the session summary basically.32:09And these are the timeline, what time user are interacting to that application, what is the flow? What, what are the different things they are doing? And these are the business transaction which is related to the session.32:29So if I go directly drill down here, so you see the user was interacting and they were taking some snapshot, screenshot basically and they're doing some touch, then they have invoked one of the business transaction.32:43Which is your mobile checkout, ok? And after that, this crash is happening to your application, right? So if I go, this is a crash, right? So it's a bidirectional correlation.32:59I can go from crash to session or I can go from session to crash also. So all the data is in a closed loop. You don't have to tie everything together by yourself. Once you onboard your front end as well as the backend.33:17Everything will be correlated by FD itself. Then you can discuss with your front end design of this application or the mobile app designer that why this crash is coming. They can help you to fix it. All the details will be here or you can directly share it to.33:34Them also, right? There there is a link which you can copy and send it to them that this crash is happening and by this crash, these many sessions are being impacted. User sessions are being impacted. All right, we'll cover one last use case for today. Okay, so.33:54We'll go on the session side, right? What, how we can troubleshoot a user session. So we have done it for the crash. Now we are just doing it for the the session which are impacted by the network performance or maybe the back end service, right?34:13So you can see this is the session which is happening on 19th of May and the timeline is there already. Okay, and the timeline you can see in session summary it will tell you how much time this session is, is lasting, what are the platform they are using, what OS version, everything is there, ok, what.34:33That they are using and their location also and the country, right? I'll go back to the timeline. Okay, you can see that user has start interacting with the mobile application and.34:53Somehow while they are invoking network requests, so there is some network request which is slow, right? Very slow basically not slow. So I'll that go directly to the business transaction. Okay, so you see the this particular business transaction.35:06It's or the network page is taking 9 s to load, right? I can go directly and see the performance for that. So you see this checkout business transaction is taking 9 s. If I go again, then the same it is related to the business transaction, backend service. Then I can click on the business transaction.35:25And again, I can go to the snapshot.35:45Sort it out with the slope response time 1 s. For the time being, I can't see I can go directly to the, to the errors if there is any one day. Okay, yeah. So we can open anything and start to show.35:48Thing right why this business transaction is throwing an error. So it is showing some 400 error which is a client's site error basically and.36:08So they don't have any UID for the checkout card. I I think the item was likely to be deleted by cleanup procedure and these are the underlying issues for that error basically. You can go directly and check here. There is some async activities happening in.36:19The application can go what is the.36:39Detail or drill down into the call graph, we'll show you where it is happening 1 s slow calls and error. These are the detail as this one. Yeah, this is the error basically.36:42Yeah, so that's, that's how you can use mobile real user monitoring in a conjunction to your backend service monitoring basically in appdynamics. So these are the different use cases which he would be, you know, like to talk about today.37:02That's it Kevin, from my side. I think we are done. Okay, so we should be, you know, open for the any question or anything to discuss about any specific use case. I'll stop sharing my screen.37:21Sure, just a quick one what is next for mobile rom? Do you have any idea of what's the new features that might be coming? So the new feature which currently coming in the session replay.37:39Okay, so session replay is basically interactive way of looking what user was doing in your application and it's a playback video, ok? Other than the, you know, troubleshooting a session normally, like we have done it in our demo.37:58Okay, there is a session to play feature which is a playback video, you can run the video and within the video you can literally see how user is interacting to your application and if at all there is a crash or error or something, then.38:16You can identify within the video also. So it's a kind of playback feature basically. Okay, thank you. How do you use this against a developer when it's come to.38:32Application error and the front end error. How do you use these information? Do you mean the sessions and alright? I believe it's when there's a scenario where there's an issue happening, the user reported.38:51How do we use this information to help us to identify APM and and it's a front end problem. So basically, you know, we can start troubleshooting from the end user perspective 1st of all, right? As I mentioned that let's say if some geolocation users are not able to interact with.39:08Your application if it is a global.39:28Or if it is a regional application, then probably your network request or the front end pages are taking much longer time to load in their user mobile devices other than the normal one. Okay, then you would like to see why today or maybe a specific time those pages are.39:30Are taking more time, right? And.39:50And if it is failing or it is throwing some HTTP error, then you would be interested to know why these pages are throwing HTTP error. So the for the underlying HTTP error to understand it more, you would like to troubleshoot and the reason could be either your application might be crashing on their devices, then you go from front.39:53And pages to the crash crash analytics and to understand why this crash is happening and what is the meaning of that crash, right? So that you can discuss with your front end developer.40:13That this particular page or mobile network requests are failing to a particular device. It could be a particular specific device or it could be, you know, group of devices, right? That is one way. The other way is, as I mentioned that the user might be, you know, complaining that they are not able to proceed.40:24To the checkout functionality or to the login functionality, any sort, right? So what you can do is you can start analyzing the user session and see where they they are having a issue in their mobile interaction, application interaction when it is started and what are the underlying services.40:45They are invoking while interacting with the mobile application. And then I mean not just backend service basically it's a complete user interaction, right?41:05And then you can identify the issue and you can ask your developer to fix it so that your user experience could not go very slow or erroneous, right? Because it's a just a user experience only if the user will not be, you know, seeing that application working seamlessly on their devices, then there is a.41:15The chance of, you know, churning the user, they would be switching back to your competitor or somewhere, and you will be end up losing your, you know, user base.41:35Alright, thank you. I think that's all the question we have. All right. Are we good? Anyone, anyone? Sorry, I just got one more. Yeah. We have been asked to talk about exp.41:46Experience journey map, which is part of the EOM I believe. Yeah, experience journey map, I'll cover it quickly. Okay, NO worries. Okay, we have spent just three or 4 min. Sure, sure, sure. So experience journey map use case comes into play.42:06Where you just, we are now troubleshooting a user session, right? So we are specifically going in a session and see why this session is being erroneous, where it starts failing. Experience journey map is basically interactive or.42:23Way of looking how your user is working in your application and what are the different steps, right? So for an example, let me share my screen again, right? User experience, let me open one application, experience journey map.42:40I'm sharing my screen ok just give me a minute. I'm just pulling out the data to showcase. Yeah, let me share my screen.43:10Are you able to see my screen? So we are now on a dashboard. We are looking at the commerce iOS application. This is the entry point of your application. So these are the users which are going to the login, then list the view and then cart view, right? So all your maybe hundred percent of.43:26Of the user base are getting segregated to different services they are interacting, and how much of the churn? Let's say this user's cart view, they, we have 5680 user.43:45And then out of that, you know, only 3129 users are the one who are, you know, doing checkout basically, right? So, yeah, there is a drop, right? So this is a kind of experienced journey map where we are seeing.43:58How many users have we started using our application? What services they are going until there and whoever are proceeding with the, you know, other services and whoever has closed the mobile apps or they are not using it anymore. So that you understand like.44:15Your I mean the funnel kind of thing, right? How many users are interacting and what services they are using most in your application? Alright, that sounds good.44:33If you have any other questions feel free to let us know. We can run an extension section if you are interested as our customer. I'm happy to run it as a one off, just reach out to us and if you want to have any further discussion around like may perhaps a seminar very 1st.44:49Focused.45:09We can also take that as a topic for the future EIS. Other than that, I think that's everything for today. Thank you. Thanks, Kevin. I think we have a good one, we'll see you. Bye. Thank you, bye bye.45:10