Impacted Users or Executions dashlet


When you create or modify a dashboard, select and configure the Impacted Users dashlet to display the number of impacted real users compared to the total number of users over the last 24 hours.

Note

Do not use the Impacted Executions option of the dashlet. The Impacted Executions option has been deprecated. BMC recommends using the Application-Health-Synthetic-dashlet or the Applications-Overview-Synthetic-dashlet instead, which show a wider time range and more detailed data.

How are users impacted?

Impacted users represents the number of active end users in the selected five-minute period that are experiencing latency issues or errors that exceed the defined thresholds.

This topic presents the following information about the dashlet:

Understanding the dashlet data

Click the application name to drill down to the Application View, which displays the same time period as displayed in the dashlet.

Dashlet requirements

The Impacted Users dashlet requires real-user application monitoring with App Visibility Manager.

The dashlet displays data over the last 24 hours. The dashlet is not affected by the dashboard time period.

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.

Configuring the dashlet

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

  1. Click Add Dashlet and select the Impacted Users or Executions dashlet.
  2. Click the Configure Dashletconfigure_icon.png icon.
  3. (Optional) Enter a descriptive title for the dashlet.
  4. Select the dashlet data type: Impacted Real Users.
  5. To choose an application, click Select to open a list of applications.

The list displays applications with App Visibility real-user monitoring.

Related topics

Analyzing-end-user-experience-with-the-User-tier

App-Visibility-end-user-monitoring

Adding and modifying dashboards
Dashlet libraryAdding and editing components

 

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*