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

A dashboard and its dashlets display either data of a System Profile live session, or of a stored session. Dashboard header shows data source and the timeframe.

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

AppMon 2017 May This description applies to AppMon 2017 May. See the 2018 February description in the expandable section below.

  • Dashlet, opened from the Cockpit, has the parent System Profile/stored session node as the data source.
  • Dashlet, opened from the Add dashlet dialog box, inherits data source from the dashboard.
  • Newly created dashboard has the same data source as the last active dashboard.

A dashlet can use a custom data source, different from the dashboard's one. 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 source won't affect custom dashlet data source.
  2. Dashboard specific data source.

To change the data source for a dashboard:

  1. Open the Source tab of the Dashboard Properties dialog box. Do one of the following:
    • Click the name of the source in the dashboard header, and select Change Source from the menu.
    • Right-click the dashboard tab, select Properties from the context menu, and then click the Source tab.
  2. If needed, select the AppMon server from the Server list.
  3. 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.

AppMon 2018 February

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.