Remote Sites Dashboard

ADEM also helps you resolve performance issues reported by specific remote sites starting from
Autonomous DEM
Remote Sites
From here you get an overall view of the experience trends for all your ADEM remote sites. You can view
  • The overall experience score for all the remote sites. This helps to determine how all sites are working with a breakdown view of the remote sites that are performing good, fair, or poor
  • The experience score for each site
  • The connected Prisma Access location sites
  • Information on the Internet and private WAN circuits that the remote site is connected to
How the Experience Scores get calculated
ADEM discovers the various paths to be monitored based on the application forwarding policies configured on Prisma SD-WAN devices. ADEM runs synthetics test on all active and backup paths per application and calculates the
experience score
per path, per application, and per site which rolls up from all remote site as organization experience score.
Experience Score for Each Path:
For each path (active and backup path) which is discovered by ADEM based on the application forwarding policy configured on Prisma SD-WAN devices, ADEM collects the following metrics:
  • Application reachability
  • DNS resolution time
  • TCP connect time
  • SSL connect time
  • HTTP latency
Each of the above metrics (other than application reachability) have a different scores and baselined lower and upper thresholds, and their combined score equals 100. The sum of these individual metric scores determines the experience score for each path. If the application reachability is zero then the experience score for that path will also be zero. If the application is reachable, only then the remaining four metrics will be calculated.
Application Experience Score:
The application experience score per remote site is an average of test samples collected from all active paths. For example, if an application for a remote site is monitored on two active and two backup paths, the average of test sample results from all active paths will be considered as an experience score for that application monitored on that remote site.
Remote Site Experience Score:
The remote site experience score is an average of all test sample results that are collected from individual applications monitored for that remote site.
Organization Experience Score:
The organization experience score for remote sites is an average of all test sample results that are collected from individual applications monitored on all remote sites.
In the
Monitored Remote Sites
table, you can drill down into details for a specific remote site that is reporting performance issues by clicking the
Remote Site Name
Remote Site Details
page opens.
  • The
    Experience Score
    in the top most widget is the overall experience score of the remote site or branch, which is an average of experience scores from all the test samples collected on active paths of all the applications monitored for that site. Although the experience score of each backup path will be individually calculated and available for each remote site and application, the experience score for backup paths are not taken into consideration when calculating the Experience Score of a remote site.
  • The
    Experience Score
    for each individual application in the
    Application Experience Details
    widget shows the end-to-end experience for the active paths of the application. It is the average of all test samples collected on the active paths for that specific application only.
  • You can see how many applications you are monitoring and also how many active and backup paths are monitored. Each application card shows the number of paths that are impacted. The red or yellow dots in the legend indicate that the path is impacted. Green stands for good.
  • Clicking on an application card shows the experience score for its active path as well as its backup path under
    Total Paths
    For both active and backup paths of an application, ADEM collects the following information, which is different for each type of path:
    • Calculates an experience score
    • The type of path (Prisma Access path (standard VPN), Secure Fabric path, or Direct Access path)
    • Its source circuit and destination termination points
      Click on a type of path (active or backup) to see the filtered data for that path type only in the widgets that follow.
  • ADEM monitors three types of paths:
    • Prisma Access Path
      Prisma Access
      Path: You can see the source circuit name extracted from the remote site, the path type (standard VPN) and the destination IPSec termination node name on Prisma Access.
    • Direct Access Path
      The Direct Access Path shows which remote site (Miami) and circuit name (att_internet_mia123), has direct access to the applications. The circuit name is derived from the name configured for the circuit on the Prisma SD-WAN controller.
    • Secure Fabric Path
      The Secure Fabric path forms a tunnel to the Prisma SD-WAN in the data center. In addition to the path type, this widget shows you the remote site name and the data center where the tunnel is terminating. It also displays the source circuit name extracted from the remote site connected and the destination circuit name in the data center.
  • In the
    Path to
    widget, you can see which segment of the network— segments starting from the remote site, ISP or WAN, or the application itself—might be the cause of the issue. For each segment, you can get the trends by clicking on the node. For example, if you click on the Prisma SD_WAN Branch node you get the CPU and memory trend, clicking on Internet will display latency, jitter, and packet loss trend.
    Path Visualization
    tab provides detailed hop-by-hop information for each node including the performance metrics for that node.

Recommended For You