Entry Points dashlet

The Entry Points dashlet shows an aggregated representation of PurePaths dashlet that started at the same entry point. It provides an overview of different types of PurePaths as well as additional statistical data such as the number of PurePaths started at a specific entry point and the average, minimum, maximum, and sum of the execution time spent by all PurePaths started at a specific entry point. You can use this information to associate a performance issue with a group of PurePaths and then to a specific PurePath instance.

Entry Points dashlet
Entry Points dashlet

Metrics

The table lists the following information:

  • Error State: The first, unlabeled column displays icons to indicate the error states of the underlying PurePaths, such as Successful or Failed Transaction Error.
  • Entry Point: A string representing the PurePath entry point.
  • Entry Method: The entry method where the PurePath starts.
  • Entry Class: The entry class where the PurePath starts.
  • Agent: The ID of the Agent that recorded the execution of the entry point, including the Agent name and the host name for the Agent. Only available if the entry points are grouped by Agent. See Aggregation Options, below.
  • Count: The number times an execution of this entry point was recorded.
  • Failed %: The percentage of failed transactions detected for this entry point.
  • Total Avg [ms]: Average duration of the execution of all PurePaths started at this entry point.
  • Total Min [ms]: Minimum duration of the execution of a PurePath started at this entry point.
  • Total Max [ms]: Maximum duration of the execution of a PurePath started at this entry point.
  • Total Sum [ms]: Accumulated duration of the execution of all PurePaths started at this entry point.
  • CPU Total Avg [ms]: Average CPU time spent for the execution of all PurePaths started at this entry point.
  • CPU Total Min [ms]: Minimum CPU time spent for the execution of a PurePath started at this entry point.
  • CPU Total Max [ms]: Maximum CPU time spent for the execution of a PurePath started at this entry point.
  • CPU Total Sum [ms]: Accumulated CPU time spent for the execution of all PurePaths started at this entry point.
  • Total Sync Avg [ms]: Average synchronization time spent for the execution of all PurePaths started at this entry point.
  • Total Sync Min [ms]: Minimum synchronization time spent for the execution of a PurePath started at this entry point.
  • Total Sync Max [ms]: Maximum synchronization time spent for the execution of a PurePath started at this entry point.
  • Total Sync Sum [ms]: Accumulated synchronization time spent for the execution of all PurePaths started at this entry point.
  • Total Wait Avg [ms]: Average wait time spent for the execution of all PurePaths started at this entry point.
  • Total Wait Min [ms]: Minimum wait time spent for the execution of a PurePath started at this entry point.
  • Total Wait Max [ms]: Maximum wait time spent for the execution of a PurePath started at this entry point.
  • Total Wait Sum [ms]: Accumulated wait time spent for the execution of all PurePaths started at this entry point.

Aggregation options

Use the Analysis tab in the Dashlet Properties dialog box to limit the entry points amount, and select the aggregation option:

  • Agent: Group entry points by Agent instance IDs, which include the Agent name and host name. Recorded PurePath entries that differ by the host name of the recording Agent are added to distinct groups, providing a more fine grained aggregation.
  • Tier: Group entry points by the Agent name, disregarding the host name. PurePath entries recorded from different Agents that have the same name are added to the same group, even if they are connected to different hosts. For example, a PurePath from myAgent@myHost:1 are aggregated with the PurePath from myAgent@anotherHost:2.