Endpoint Agent End-user Experience

Last updated: Mon Feb 04 23:41:05 GMT 2019

This article addresses the effects of installing Endpoint Agent from the end-user perspective.  You may also be interested in the ThousandEyes Endpoint Agent End-User FAQ, a publicly available webpage on the ThousandEyes site which can be used to answer some common questions that your users might have.

In general, end users will not see any degradation of system or network performance as a result of the Endpoint Agent. A button to start or stop manual recording of an Endpoint Agent session will appear in the user's browser and the ThousandEyes Endpoint Agent will be listed in the browser's installed extensions/plug-ins.  Additionally, the Endpoint Agent will run a small number of processes that will be visible in a process listing.  The details of these changes depend on the operating system and browser, and are listed below.

Windows

Browser Plug-in

When recording browser activity manually, users will see a popup window bar that says “Recording Started.” The popup will disappear when users click the same button to stop recording, or if the user closes the browser tab.
  • Chrome:

Windows-Chrome Endpoint Agent recording

  • ​​Internet Explorer:

    Windows-IE Endpoint Agent recording

Processes

  • te-agent
    The system service responsible for gathering system and network data, receiving new configurations, and sending data back to ThousandEyes. Runs in the SYSTEM context.
  • te-browserhelper
    The process that accepts performance data from the browser plug-ins and forwards the data to te-agent. Runs in the user context.
  • te-updater
    The process responsible for checking for and installing updates. Runs in the user context to download updates, and in the SYSTEM context to install updates.
  • te-proxy
    This process is run only if a browser proxy configuration is used and available in the user context, and is not available to the system service (running in SYSTEM context). te-proxy runs in the user context and bridges contexts so that te-agent and te-updater can communicate over the network with ThousandEyes through the configured browser proxy.
File locations
Files are installed in the C:\Program Files (x86)\ThousandEyes\Endpoint Agent folder by default.
Log files:
  • C:\Program Data\ThousandEyes\Endpoint Agent\log
  • Chrome: C:\Users\$user\AppData\Local\ThousandEyes Endpoint Agent\log
  • Internet Explorer: C:\Users\$user\AppData\LocalLow\ThousandEyes Endpoint Agent\log

Mac OS X

Browser Plug-in

ThousandEyes Endpoint Agent browser extension executes in Chrome. When recording browser activity manually, a bar appears that says “Recording Started.” The popup will close once you stop the recording or close the tab.

MacOS-Chrome Endpoint Agent recording

    Processes:

    • te-agent
      The system service responsible for gathering system and network data, receiving new configurations, and sending data back to ThousandEyes.
    • te-browserhelper
      The process that accepts performance data from the browser plug-ins and forwards the data to te-agent.
    • Crashpad (2 instances)
      An open source Mac OS X crash reporting client for Chrome.

    File locations:

    ThousandEyes Endpoint Agent application in the Applications Folder.
    Log files:
    • /Users/$user/Library/Application Support/ThousandEyes/Endpoint Agent/log
    • /Library/Application Support/ThousandEyes/Endpoint Agent/log