Embrace provides the options to create custom dashboards to offer a better way to dig into your data. Any individual user can make a dashboard. Once their dashboard is published, it will be visible to your entire organization.
TABLE OF CONTENTS
- Types of Dashboards
- Creating a Widget in a Dashboard
- Creating a Comparison Dashboard
Types of Dashboards:
There are two different types of dashboards: Widgets and Version Comparison dashboards.
We’ve gone ahead and created one of each for you. Both the Version Comparison & Health and Trends can be easily duplicated if you do not want to create a dashboard from scratch.
The Health & Trends Template is a “Widget” dashboard. Widgets are individual tables or graphs that track one or more metrics and are great for digging into specific metrics. The Comparison dashboard is most helpful for comparing data across different segments.
When configuring either type of dashboard, name and save the dashboard before closing or refreshing the page. The "Preview" feature provides you with the opportunity to review your dashboard before publishing.
Creating a Widget in a Dashboard:
Widgets can help to expose trends in data like:
- Crash counts over time, broken out by app version and user personas
- Moment median duration (e.g. startup) over time
- Count of error logs, broken out by OS version, focusing on the US and Canada
- Median session duration over time, broken out by country and app version
To create a widget, click "Add Board" and then "Widget " on the dashboard page.
From here, there are many options to select different widgets based on various data sources to allow you to visualize the data. The "Customized Data" tab allows you to configure a widget from scratch.
For example, to create a widget for Network data, on the dashboard page, select "Create Widget" and either the "Customized Data - Networking" or "Requests".
Next, select how the data should be presented; a graph or a table.
After selecting the visualization, choose specific metrics to visualize. We can utilize the "Group by" and "Filters" features to break down the data into different categories and exclude data on a given condition.
Filters are further refinements to the data. For example, if you want to know how your network requests perform on the latest OS versions, use the filter to only include data for those versions.
⚠️ Note: Remember to name and save the widget before closing or refreshing the page.
Graph Visual Example:
Table Visual Example:
For this example, we look at Network Requests grouped by app and OS versions with connection errors. Unlike the graph visual, the table visual gives the option to group by more than one field.
⚠️ Note: To enhance the size of the widget or to view the widgets in TV mode, select the three little dots and the correct size.
Creating a Comparison Dashboard:
By easily comparing metrics as new versions are released, teams can immediately spot regressions worth investigating.
Comparison dashboards can help to answer questions like:
- Which app versions are experiencing the most crashes or uncategorized exits (UE)?
- Is startup time getting slower in newer releases?
- Which user segments are the most valuable to the company?
- Are users in different countries having vastly different app experiences?
- What groups of users use the app more frequently and for what periods of time?
To create a Comparison dashboard, select "Add Board" then "Comparison " on the dashboard page.
We can configure how we would like to compare the Segments on this page.
Segments are the groups you want to compare your metric across. For example, if you wanted to monitor crash counts across app versions, then app versions would be your segment. If you wanted to monitor failed network requests across OS versions, then OS versions would be your segment.
Clicking "Show Notes" will provide a brief description of how to build the segment.
You must specify the comparison to be either “in order” or “against one group”.
“In order” means that segment 2 will be compared to segment 1, segment 3 will be compared to segment 2, etc. When looking for improvements or regressions in a metric, each segment is compared against the one that comes before it.
In the example graph below, app version 4.34.2 has a lower crash count than 4.33.6. The number is green to highlight this change as an improvement. However, 4.34.5 has a higher crash count than 4.33.6, so this number is red to indicate a regression.
“Against one group” means that we select one segment as a control group, and every other segment is compared to that one for highlighting improvements/regressions. See the below table for an example. Since both 4.33.6 and 4.34.5 have higher crash counts than the control group 4.34.2, both of their crash counts are in red.
Next, set the Filters and Metrics. Metrics are the underlying measurable that you’re interested in. Embrace supports a wide variety of metrics, covering crashes, logs, network requests, ANRs, cold starts, and more.
For this example, we selected the Top App Versions that we would like to use for the Segments. Then we filtered on the Country OS, specifically the US and Canada, and chose the Crash Count, OOM Session Count, and User Terminated Sessions metrics. We also included a graph to visualize crash count trends.
Select "Preview" in the top right-hand corner to review your Comparison dashboard before publishing.
If you need assistance with creating dashboards, please do not hesitate to reach out to us! We are here to help.