What’s really neat about Application Insights is that User Timeline pane you see on the right.
APP INSIGHTS PRO
The timeline view will illustrate how long each request has taken to complete and the side pane will show you all the details that a pro developer will be interested in reviewing. Especially the creation of a new row in the Dataverse table is probably something of high interest to customized apps, so keep this in mind when planning how you gather performance metrics for your business critical applications.ĭrilling deeper into the Dashboard Load operation, we are presented with a detailed list of resources that a model-driven Power App will perform when requesting data from a multitude of different tables, web resources and other dashboard elements. Launch App, EntityList Load, EntityForm Load, Dashboard Load, QuickCreateFormLoad are types of events supported today, whereas a form save event or a click on the Command Bar buttons is not yet within the OoB scope of model-driven Power Apps telemetry. This is a good moment to check the documentation on available telemetry events for model-driven apps. In our example, we’re looking at a Dashboard Load operation. You’ll see a new pane open up with a list of tracked operations, where Application Insights is smart enough to suggest you drill into one that had a longer duration than the others. Open an operation of your choice, then click samples in the “drill into” section of the side pane. You’ll see a list of operations that you can sort by longest average duration, for example. So, inside your Azure Portal and the Application Insights resource, go to Performance and choose Browser. Server calls to specific APIs may well be interesting for a highly customized Dynamics 365 system, for example, where you’ve got a bunch of plugins running custom logic and potentially connecting to external data sources.įor exploration purposes the browser side activity is probably a better starting point. Since the model-driven Power Apps are so deeply tied with data stored in Dataverse (although virtual tables are becoming a no-code option as well), this new Application Insights integration tracks both the client and server side actions resulting from end user app usage. Once you’ve provisioned it & connected it to the Power Platform environment of your choice, data will start pouring in almost instantaneously.
APP INSIGHTS HOW TO
We see here that the Export to Application Insights feature is configured for one selected environment only, but you can run the wizard multiple times to add more environments later.īefore you can complete the configuration wizard, you’ll need an existing Azure resource for Application Insights, so check out the docs for how to create one. You’ll see the option to set up App Insights integration, which actually shares the configuration pane together with the Export to Data Lake feature (which I’ll cover in a future blog post). To get started, you should open Power Platform Admin Center (PPAC) and go to Analytics – Data export (preview). Configuring Application Insights telemetry for your app’s environment So, this new integration finally inspired me to explore what capabilities Application Insights offers to app makers and admins. While I do enjoy building simple canvas apps myself, too, at the end I’m a model-driven guy that can get the job done a lot quicker when given a Dataverse environment. Timo Pertilä, has written both an introduction and a deep dive blog post on that topic. My colleague & canvas guru extraordinaire, Mr. Today it’s time to dive into another preview: Analyze model-driven apps and Microsoft Dataverse telemetry with Application Insights.Ĭanvas apps have had a built-in integration with Azure Application Insights for over a year already. In my previous blog post I looked at the new tenant-level reports in Power Platform Admin Center. Microsoft has released a wealth of interesting new administration capabilities for Power Platform in the last few days.
0 kommentar(er)
