Application Client Breakdown dashlet

When you create or modify a dashboard, select and configure the Application Client Breakdown dashlet to identify real-time issues that might depend on how end users access your application. You can break down the way users access the application—by browser type or by platform—and display the average application end-to-end time or the number of hits per second for each client breakdown.

For example, the following image displays two instances of the dashlet: browser type by average response time, and browser type by number of hits per second:

The graph on the left shows that users of the Android native browser have greater peaks and variations in average response time. The graph on the right shows that the volume of users, as shown by the number of hits per second, on that browser is relatively low. In this way, information from the graphs can help you prioritize issues.

This topic presents the following information about this dashlet:

Understanding the dashlet data

By default, the dashlet displays the average response time for end users, aggregated by browser, for all applications with App Visibility end-user monitoring.

The following image displays the default Application Client Breakdown dashlet, showing average response time by browser type.

Application Client Breakdown dashlet: browser type by average response time

The selected time filter in the image is set to the last two hours, which is determined by the dashboard Time Period setting. For more information about setting the time for the dashboard, see Adding and modifying dashboards .

You can examine information about data points on the graph by performing the following tasks:

Dashlet requirements

The Application Client Breakdown dashlet requires end-user monitoring with App Visibility Manager.

When you configure the dashlet, you select the following options:

• Aggregate data by browser type or by platform.
• Display the average response time or the number of hits per second for the selected aggregation.
• Display data for one ore all applications that use end-user monitoring through App Visibility Manager.

When you configure the dashlet, you select an application. If you use the dashboard application filter to select an application, the dashboard filter overrides the dashlet's selected application.

For optimal viewing, use a dashboard row that is at least 33% wide.

Configuring the dashlet

You can configure this dashlet when you add or edit a dashboard .

1. Click Add Dashlet and select the Application Client Breakdown dashlet.

2. Click the Configure Dashlet icon.

3. (Optional) Enter a descriptive title for the dashlet.

4. From the Aggregate By list, select the client breakdown to display:

   • Select Browser to aggregate data by browser type.
     Monitored browsers consist of Android Browser, Chrome, Firefox, Internet Explorer, and Safari.
     Browsers that are not recognized are listed as Others. To add monitored browsers, contact BMC Support.

     Note

     For Android devices version 4.4 (KitKat) and later, Android Browsers use a Chrome engine and are categorized as Chrome.

   • Select Platform to aggregate data by client platform, such as by desktop or laptop computer users, or by mobile device users.
5. From the Data Type list, select the type of application data to display:
   • Select Avg Response Time to display the average latency for users of the client breakdown (browser or platform).
   • Select Hits/Sec to display the number of hits per second by client breakdown (browser or platform).
6. Choose to display results from all applications or from one application:
   
   • Select All to display results from all applications.
   • Select Selected, and then click Select to open a list from which you can choose a single application to display.
     
7. Select the height of the dashlet row: 1X, 2X, 3X, or 4X.
   The value of X is approximately 100 pixels. The default height is 3X.

Related topics

App Visibility end-user monitoring

Adding and modifying dashboards

Dashlet library

Adding and editing components