Dashboard data scope

This page describes AppMon strategies to quickly display relevant data in the dashboard of choice and how you can influence things.

Data source

Dashboard and its dashlets display data of the System Profile/Stored session, currently selected in the Session selector. Dashboard header only shows the timeframe.

Dashboard header shows time scope
Dashboard header shows time scope

To change the data source for a dashboard, simply select the required Server and/or System Profiles/stored session from the resource selectors. All the dashboards and dashlets switch to this data source, unless custom data source is set.

You can set a custom data source for a dashboard and/or a dashlet. The header of the dashlet with custom data source displays the icon. Priority of data sources is the following:

  1. Dashlet specific data source. Change of dashboard data custom source or server/session in resource selectors won't affect custom dashlet data source.
  2. Dashboard specific data source. Change of server/session in resource selectors won't affect custom dashboard data source.
  3. Resource selectors.

The header of dashboard with custom data source shows data source and the timeframe.

Dashboard header shows custom data source and time scope
Dashboard header shows custom data source and time scope

To set the custom data source for a dashboard:

  1. Select the required dashboard in the dashboard selector, then right click it and select Properties from the context menu.
  2. In the Dashboard Properties dialog box click the Source tab.
  3. Deactivate the Use select client data source checkbox.
  4. If needed, select the AppMon server from the Server list.
  5. From the Session list, select a System Profile, or a stored session.

To change data source for a dashlet:

  1. Open the Source tab of the Dashlet Properties dialog box. Do one of the following:
    • Press Alt+Enter, to open the Dashlet Properties dialog box and then click the Source tab.
    • Right-click the dashlet tab, select Dashlet Properties from the context menu, and then click the Source tab.
  2. Select the Enable dashlet specific data source check box.
  3. If needed, select the AppMon server from the Server list.
  4. From the Session list, select a System Profile, or a stored session.

Some dashlets, for example Incidents dashlet, may be configured to show session independent server-wide data. The header of such dashlets contains global global icon. Change of session doesn't affect dashlet data, but the change of server does. To set dashlet as session-independent:

  1. Open the Source tab of the Dashlet Properties dialog box. Do one of the following:
    • Press Alt+Enter, to open the Dashlet Properties dialog box and then click the Source tab.
    • Right-click the dashlet tab, select Dashlet Properties from the context menu, and then click the Source tab.
  2. Select the Use session independent data source check box.

AppMon 2018 October Dashlet filter subscription

By default, dashlets get data from the analyzer, which prepares a set of data according to dashboard/dashlet filtering parameters for every request. Querying same data multiple times consumes a lot of server resources, leading to long response times to deliver results.

You can decrease the server load by subscribing to certain dashlet configurations. In that case, data is pre-calculated and stored in the analysis cache; and all dashlets with this configuration retrieve the cached data.

A subscription has the following parameters:

  • The type of the dashlet
  • The parameters of the analyzer, excluding drill-down limit and result limit.
  • The criteria of filters applied to the dashlet—on both dashboard and dashlet levels. The following filters are not supported: timeframe, visits, and Business Transactions.

The possible number of subscriptions depends on your deployment size.

Deployment size Subscriptions limit
Demo 10
Small 25
Medium 50
Large 75
xLarge 100
xLarge64 150
xLarge96 200
xLarge128 200
xLarge256 250
Required permission

To set a dashlet filter subscription, you need the Manage cached analysis results permission assigned to the Server Management role.

To set a dashlet filter subscription:

  1. Set all the required filters as needed.
  2. Right-click the dashlet and select Subscribe dashlet filters from the context menu.
  3. In the Name filed, type the name for the new subscription.
  4. The subscription is applied to the dashlet automatically.

All the dashlets, matching the criteria, use the subscription automatically. To force a dashlet to use the standard mode, right-click it and select Ignore subscription filters from the context menu.

Cached data is stored in several-minutes chunks. If available data doesn't match the selected timeframe a warning message appears at the top of the dashlet.

Timeframe mismatch warning

Click it to use the standard mode.

You can find the list of configured subscriptions in the Subscribed Dashlet Filters item of the Dynatrace Server Settings dialog box.

Quick vs. Full Analysis

A partial analysis is performed to provide instant feedback when opening or refreshing a dashlet is estimated to take a long time. (due to the amount of data and/or filter criteria) Then shown are only representative data from the selected time frame. To give an indication of the accuracy of the result, the number of analyzed vs. total transactions is displayed.
A quick analysis is never performed in dashlets where it is important to see every transaction, such as PurePath, User Actions, or Visits. When AppMon performs a quick analysis, the dashlet displays the message as shown in the following figure. Click full analysis to analyze all transactions.

Analyzer progress visualization

While an analyzer job is running, its progress is visualized at the top of the dashlet.

The results for the data analyzed so far are shown in the dashlet. A blue information bar shows how much of the session was analyzed when the analysis was stopped.

Analysis stopped due to PurePath limit reached

The analysis is stopped by the AppMon Server if the PurePaths limit is reached. This limitation is not related to the number of PurePaths you are able to store on disk. This PurePaths limit ensures that the AppMon Client does not run out of memory when displaying the data.

A blue information bar indicates that the analysis was stopped by the Server and shows the number of analyzed PurePaths. The recommended response is to switch to a smaller timeframe for analysis. Use the arrow buttons in the toolbar to navigate through the PurePath history.

Analysis cache

AppMon continuously does an analysis of the incoming data in the background and caches the results.