Tracing can also help diagnose various issues as you can send a trail of information as your users navigate through your app and perform various actions. Use Trace to provide more granular usage information for controls on screens, which specific users are accessing your app or even what errors are occurring. Using the new Tracefunction, you can also write custom traces directly to App Insights and start to analyze information specific to your scenario. App performance, Funnels and Cohorts and plenty more out-of-box features of App Insights can be further explored here.
I’ve just given you a small sample of the capabilities in App Insights. Can you reduce clicks and optimize the paths to the most popular features for your end-users? You can use this view to analyze the most used navigation paths. User Flows is another great visual which shows how users navigate around your app. For example, you may want to stop future investments on specific screens due to low usage and prioritize other features in the app. You can use this information to analyse and understand screen usage or feature adoption in your app and make data-driven based decisions on your next features. In the Events view, you get a summary of all the screens viewed across all app sessions. Drilling into one of the user sessions, you can explore detailed information such as the session length, the screens visited and also low-level transaction details. Details about where the users are located and the browsers and operating systems they use are also displayed. In this view, you can see how many people have used the app (these are not unique users, but I’ll have more about that later), the number of sessions for the app and the number of events logged. Open the App Insights resource you created and select Users in the left navigation menu. Let’s view the events and see the insights you have generated from adding the instrumentation key to your app.
Screen navigation events will get automatically logged to App Insights along with usage information on where the app is getting accessed from and on which devices and browsers. Great! That’s all you need to start gathering telemetry for the app! Play the published app and navigate to various screens.
Application insights update#
After you update the instrumentation key, save and publish your app. In the App object panel, update the Instrumentation key property to your Azure App Insights instrumentation key. Open your app and the select the App object. After you create your App Insights resource, you are going to need the instrumentation key so copy or take a note of this value. To create an App Insights resource, you can follow the documentation here. Getting startedīefore you can send telemetry for an app, you will need to create an Azure Application Insights resource to store the events. Would you like to know how many people are using your App, where they are accessing it from, what screens are most visited, the devices or browsers that are most popular? Or maybe you want to monitor all errors presented to your users, and using this data, get automatically alerted if errors suddenly increase? With your app connected to Azure Applications Insights, you can now begin to gather this information to help you drive better business decisions and improve the quality of your apps. I’m thrilled to announce a new instrumentation feature to allow makers collect detailed telemetry for their Canvas apps.
0 kommentar(er)
