As you may know in the latest Studio update we have delivered a possibility to export Studio’s telemetry data to your own Azure Application Insights instance. This data allows you to monitor and analyze what users are doing in Studio.
- configure your own Azure Application Insights instance
- configure Automation Ops on your tenant
– create a policy and put the instrumentation key of your Insights instance to the Application Insights target section in the policy Feature Toggles tab.
Don’t forget about pushing the policy to the right target. You can do this by choosing the policy for the right level: Tenant, Groups or Users (you can read more about it here).
After completing all of the steps above, your Azure Insights instance will start receiving events that you can consume by querying the database using the Kusto language in the Logs console. All of those events are part of the
You can now visualize your data by building a useful dashboard. Such a dashboard could be produced with Power BI and its capability to directly link to the Azure kusto queries. This will drastically improve your company metrics and will help you monitor your development environment.
The main difficulty is that this requires writing a lot of queries, exporting them to PowerBI and then designing every single chart from scratch. To make things simpler, we prepared a sample dashboard that you will be able to easily import and save a lot of time. It consumes some basic telemetry events and converts them to neat charts based on your own data.
To get things going, we created a simple UiPath Studio project that will require simple input and will guide you through all the steps.
See this simple video that gives an overview of all the steps:
The sample dashboard contains:
- History of Studio sessions - date, username, the studio version, session duration.
- User engagement - how many days a user was active in a month.
- Timezone measurement - how many users work in which timezone.
- Packages usage and activities usage - how many packages and activities were used recently and how many times.
- History of package installation - when and who installed what and in which version.
- Top 10 most used (installed) packages.
- Projects history - consists of data related to projects like project name, project type, username and date.
- Processes run history - who, from where a process was started.
- A ratio of projects run between a local computer and the Orchestrator.
- Projects created vs. projects published - see how many projects end up in the Orchestrator.
- Projects published history - date, username, path and publish location.
- Project published by a type - how many projects and which type were published recently.
- "Run to this activity" feature statistics.
- History of activities properties change.
- Top 10 activities where a property was changed.
Below you might see an example of how the dashboard is looking like.
The DataFlow file is by default set to query for data for the last 60 days. You can easily extend that by editing every table in the DataFlow file.
Do not forget to grab a project that I described in the video
BI_DashboardCreate.zip (481.8 KB)
Let us know what do you think. We are waiting for feedback.