Monitor a User or Device (Monitor User Experience)

The Monitor User Experience dashboard displays a detailed log of all recent activities performed by all users on a single device, or performed by a single person who used multiple devices.

For example, if several people recently signed in to the same device, you can check if performance is slow for all users on this device, or just a specific user. Conversely, if one person uses several devices, use this dashboard to see whether a performance problem appears in all those devices, or just a single device.

There are two variants of the same dashboard, depending on whether you chose to monitor a user or a device on your way in to this dashboard:

  • If you access the dashboard with a username to monitor that user, it displays all activities performed by this user on one or more devices.

  • If you access the dashboard with a device's hostname to monitor that device, it displays all activities performed on this device by one or more users.

The Monitor User Experience Dashboard
To... Do this...

To view a log of recent activities performed on this device or by this user

View the Experience section of the dashboard (see below).

To view the devices used by this person

When you enter this dashboard, enter a username to view all devices associated with that person, then view the Devices section of the dashboard.

To view all the recent people who used a single device

When you enter this dashboard, enter a device's hostname, to view all activities by all those who used this device, then view the Users section of the dashboard.

To view the applications which have poor performance for this user or on this device

View the Applications section of the dashboard (see below).

To view a summary of the recent volumes of activities and their statuses during the dashboard's timeframe, view the Trends section.

To determine if a problem is due to a user-based setting on this device, or if it is caused by a system setting which applies to all users on this device

If this device was used by more than one user, when you enter this dashboard, type a device's hostname, then view the activity statuses for all users in the Applications section.

Then select one user at a time from the Users section to view if the statuses change or remain the same. If they change, it is due to a user's settings. If the statuses remain the same, the problem is either due to a system setting, or to a setting common to all the users of this device.

To determine if the status of a particular activity changes over time

Select the activity in the Experience section and view the graph below.

Troubleshoot a long backend time (part of a slow response time) of a user's activity, by drilling down from the activity into SteelCentral AppInternals™.

Investigate server-side delays. Identify an activity which contacted one or more servers, which is slow due to a long backend time.

Drill down to AppInternals to monitor each call to a server's back end components.

For details, see the step below.

To view the performance of an app's activities for all users, or only those in a single location or department

Try the Monitor Application dashboard (learn more).

Tip

To see the raw data behind this dashboard, access our REST APIs in Excel or PowerBI (learn more). View this specific dashboard's data with the BUSINESS_ACTIVITIES_RAW. Learn more.

Procedure

  1. Step 1 Open a browser and sign in to Aternity.
  2. Step 2 Select Main Menu > Monitor > User Experience.
    Accessing Monitor User Experience

    Alternatively, type the username or hostname into the search box on the top bar.

  3. Step 3 Select the user or device to display in this dashboard.

    You can either select a user to monitor all activities performed by this person on all their devices, or enter the hostname of a device to monitor all the activities performed on this device by one or more users.

    Select user or device to display in Monitor User Experience dashboard
    Field Description
    Enter a username or device name

    Start typing the name of the user or the hostname of a device, and select a choice from the auto-complete menu.

  4. Step 4 Select Go.
  5. Step 5 To view a recent log of activities performed on this device or on multiple devices by this user during the dashboard's timeframe, view the Experience section.
    Tip

    View only the types of entries you need (like activities or application events) by selecting them from the drop-down menu at the top of this section.

    View the recent log of activities for this device or user
    Field Description
    Recorded At

    Displays the date and time when the user performed this activity, according to the Time Zone at the top of the screen.

    Application (only in dashboards with multiple applications)

    Displays the name of the monitored application, as it appears throughout the system. You can customize it when you add it as a managed application.

    Activity / Event

    Displays the name of the activity as defined in the system, or the name of the health event of the device.

    Response Time

    Displays the response time of the activity.

    Activity response time splits into network, server and client time

    Use the actual response times (not scores) to check the performance of chronic (long term) problems. You cannot rely on measurements based on the recent baselines, as those responses would be chronically slow for some time, thereby skewing baselines to make those times look normal.

    Latency

    (Displays only for virtual desktops, virtual application servers or users who are using these devices) Displays the overall latency for virtual sessions (or lag) in seconds for each type of virtualized environment (virtual desktops and virtual applications), gathered from latency measurements taken every minute.

    You can view more information and drill down to other dashboards to investigate further, by hovering your mouse pointer over a result in the Response Time column. You can drill down to the following dashboards:

    Viewing more details on a specific response time
    Field Description
    Application (only in dashboards with multiple applications)

    Displays the name of the monitored application, as it appears throughout the system. You can customize it when you add it as a managed application.

    Activity / Event

    Displays the name of the activity as defined in the system, or the name of the health event of the device.

    Recorded At

    Displays the date and time when the user performed this activity, according to the Time Zone at the top of the screen.

    Status

    The status of an activity is based on one response time compared to the recent expected (baselined) response time. The statuses are measured in severity: Normal , Minor , Major or Critical .

    Activity response measured time with a status
    Activity Response

    An activity response is the time taken for an application to complete an activity in seconds.

    Activity response time

    Use the actual response times (not scores) to check the performance of chronic (long term) problems. You cannot rely on measurements based on the recent baselines, as those responses would be chronically slow for some time, thereby skewing baselines to make those times look normal.

    Backend Time

    Backend time is the time required by all the servers to process data on the backend, which is part of the overall response time of an activity. It starts when the client sends a request to the target server, when the last message of that request arrives at the target server side. It ends when the server sends out the first message of its response.

    Definition of backend time in a client-server application
    IP Address

    (Windows, Mac) Displays the device's internal IP address (including IP v6 if the device runs Agent 10 or later) which it uses to connect to Aternity.

    (Mobile devices) Displays the IP of the WiFi connection if the device is reporting data via WiFi.

    Network Time

    Network time is the total time (union) taken for all messages to cross the network in either direction, between the client and the target server, while performing an activity. This does NOT include the time used for processing the request on the server (backend time).

    Network time is the time for all messages to cross the network and back as part of an activity response
    Client Time

    Client time is the time used by the device itself as part of an activity to process data before sending its first message request to the server and after the last message response arrives back from the server.

    Client time is the time on the device side to process data as part of the activity response
    Incoming Traffic / Outgoing Traffic

    Aternity reports the total volume of network traffic in KB in both directions while an application performs an activity.

    Baseline

    Displays the typical response time (in seconds) for this activity for this user or device.

    Baseline Major

    The Major baseline threshold is a response time for a specific activity which is significantly slower than expected. Anything slower than this threshold changes the activity's status to major (), which is a call to action, because it is a major departure from the expected performance time. By default, the major threshold is set at the slowest 3% of all response times (97 percentile) for each activity in each location.

    Baseline Minor

    The Minor baseline threshold is a response time for a specific activity which is slower than expected. Anything slower than this threshold changes the activity's status to minor (), because it is a minor departure from the expected performance time. By default, the minor threshold is set at the slowest 10% of response times (90 percentile) for each activity in each location. If the activity is faster than this time, its status becomes normal ().

    Percentile

    Displays the percentage of activities whose response time is at or below this Activity Response value.

    External Threshold

    The External threshold represents the maximum response time (in seconds) of an activity as defined in your official service level agreement (SLA) with your customers. Any response longer than this threshold is colored red in the SLA dashboard, since it breaks the official SLA commitment for this activity.

    Internal Threshold

    The Internal threshold is the response time (in seconds) of an activity which would be your early warning, showing you are at risk of exceeding your official service level agreement (SLA) with your customers. Any response longer than this threshold is colored yellow in the SLA dashboard, as it warns you risk breaking the SLA commitment for this activity.

  6. Step 6 View the recent performance for this user or this device in the Trends section.

    It displays the volume of each activity status at set intervals across the timeframe of the dashboard.

    View the recent trend of performance for this device or user
  7. Step 7 View the applications with poor performance and the impact for this user or on this device in the Applications section.

    It displays the percentage of each activity status, and the impact of a slow activity by showing the number of activities for each status.

    For example, if the performance of your mail application is poor for 5% of the time for this user, check to see the number of times they actually experienced the slowdown. If the volume is just 1, the impact is minimal.

    View the performance of applications for this user or on this device
    Field Description
    Application

    Displays the name of the monitored application, whose performance metrics (activity statuses) are displayed in this row.

    Percentage Spread of Statuses

    Displays the percentage of each activity status for this application during the dashboard's timeframe.

    Volume of Activities per Status

    Displays the impact of any slowdowns in performance, by showing the number of times this device or this user reported each status.

  8. Step 8 View the performance of activities on this person's device(s) in the Devices section, and the impact of any problems by seeing the spread of activity statuses.

    If a problem is based in user settings, you can expect to see the same problem in all devices. But if the problem is specific to a single device, it would only appear in one of the rows.

    Tip

    This section is only visible if you enter a username when accessing this dashboard.

    View the devices accessed by this user
    Field Description
    Hostname

    Displays the hostname of the monitored device. View it in the Windows Control Panel > System > Computer Name, or on Apple Macs in System Preferences > Sharing > Computer Name.

    (Mobile) Displays the Device Name field. You can customize the hostname of iOS or Android devices running your enterprise's app, so device names appear in the dashboards with a consistent naming policy. For example, you can dynamically assign the device name according to the enterprise username of the app.

    Username

    Displays the username signed in to the device's operating system.

    Device Type

    Displays the type of device reporting performance to Aternity.

    Activity Statuses by Percentage

    Displays the performance of this device by showing the percentage of activities with each status.

    Activity Statuses by Volume

    Displays the impact of the performance of each activity status on this device by showing the number of activities reported with each status.

    For further information, you can drill down to:

  9. Step 9 View the list of users who recently signed in to this device in the Users section.
    Tip

    This section is only visible if you enter a hostname when accessing this dashboard.

    View the performance of the various users who accessed this device
  10. Step 10 To view the spread of activity responses for a single activity in a single row, select Distribution from the drop-down list in the Experiences section.
    An activity with its response times

    Faster activities are displayed to the left, while slower ones are shown to the right.

    Select Distribution to display all instances of an activity in the same row
    Field Description

    Green activity

    A green activity has a normal status, when its response time is as expected, which is less than the minor baseline for this activity.

    Yellow activity

    A yellow activity has a minor status when its response time is slower than expected, since it passed the minor baseline for this activity.

    Orange activity

    A orange activity has a major status when its response time is significantly slower than expected, since it passed the major baseline for this activity.

    Red activity

    A red activity has a critical status, when the activity failed to respond.

    For further information, you can drill down to:

    To view a less compact version of this graph, showing the response times of an activity, select an activity in the Experience section.

    View an activity's response times with its thresholds for this device or user

    If you want to see the value of a baseline or a threshold, hover over the relevant line.

  11. Step 11 To view the recent trend and the detailed log of activities for a single application or a single device or user, select the application (or one of its statuses), or select a device, or user, and view the log in the Experience section.
    Viewing the activity statuses for a single application or single device / user
  12. Step 12 (Only if Aternity is integrated with NetProfiler) Troubleshoot slow network times by viewing a device's network connections and traffic in NetProfiler.
    Check network traffic for this device

    Hover your mouse over an activity whose status is major () to view the breakdown of its client, network and backend time.

    Check a slow network time by opening this device at that time point in NetProfiler
  13. Step 13 (Only if Aternity is integrated with AppInternals) Troubleshoot a long backend time (part of a slow response time) of a user's activity, by drilling down from the activity into SteelCentral AppInternals™.

    Hover your mouse over an activity whose status is major () to view the breakdown of its client, network and backend time. Check if the backend time is the main culprit for the slow response time.

    For example, you can drill down on an activity to trace the server call as an AppInternals transaction, and follow it across the backend components.

    You can trace a single end user activity which triggers more than one backend transaction, viewing them all in AppInternals. An activity can trigger two calls to the same server, or to two different servers.

    Troubleshoot a slow backend time by drilling down to AppInternals
    1. a Identify an activity which contacted one or more servers, which is slow due to a long backend time.

      Hover your mouse over an activity whose status is major () to view the breakdown of its client, network and backend time. Check if the backend time is the main culprit for the slow response time.

      Identify an activity whose backend time needs investigating
    2. b Drill down to AppInternals to monitor each call to a server's back end components.

      This requires you to sign in to AppInternals. To sign in to AppInternals SaaS with SSO, it must use the same identity provider as that configured for Aternity.

      Drill down to view this transaction in AppInternals
      Field Description
      View Transactions in AppInternals

      Select to drill down to AppInternals to view the transactions resulting from this activity's call to the server.

      View Pages in AppInternals

      If an activity occurs on a web page, you can drill down to AppInternals to view the transactions plus all other transactions which originated from that instance of the web page.

    3. c Select View transaction details in AppInternals to narrow down the segment of the transaction which caused the delay in backend time.

      For more information, see the online help for AppInternals.

      View server side details of the transaction
  14. Step 14 You can jump straight to related dashboards using the quick jump menu at the top of the screen:
    Quickly jump to related dashboards
    Field Description
    Troubleshoot

    Jump to the Troubleshoot Device dashboard for this device, to see any recent notable changes in configuration, and view key performance indicators for troubleshooting problems on this device.

    Device Details

    Jump to the Device Details dashboard for this device to view all the device's static attributes.

    Activity Resource Analysis

    Jump to the Activity Resource Analysis dashboard to correlate an activity's performance with the device's resource usage.

    View in NetProfiler

    (If Aternity is configured to point to NetProfiler) Troubleshoot slow network times by viewing a device's network connections and traffic in NetProfiler. See the traffic flow in this area of the network, or perhaps other subnets which may clog access to a shared network component.

  15. Step 15 You can limit the display of this dashboard using the menus at the top of the window.
    Select the data to display in the dashboard
    Field Description
    Time Zone Selection

    Select the time zone to view the times associated with the data in this dashboard:

    • Default displays the time zone set in most Aternity dashboards.

    • Yours displays the time zone of your computer where you are viewing the dashboard.

    • Device displays the time zone of the monitored device which is the focus of this dashboard's content.

    Timeframe

    You can change the start time of the data displayed in this dashboard in the Timeframe menu in the top right corner of the dashboard.

    You can access data in this dashboard (retention) going back up to seven days.

    This dashboard displays raw data in real time, refreshing every time you access it or whenever you manually refresh the browser page.