Mobile Endpoint Agent Installation on Android Devices
The Mobile Endpoint Agent is a network performance tool that provides near real-time visibility into mobile devices, applications, and network environments. It helps IT teams and end users quickly identify and resolve network issues, ensuring optimal application performance and a seamless user experience.
Key features include continuous monitoring, real-time alerts, intuitive dashboards, and easy deployment. The Mobile Endpoint Agent can also help to monitor services like inventory management and asset tracking, offering end-to-end visibility and actionable insights to maintain productivity and efficiency. It enables IT support teams to deliver high-quality service to mobile workforces and enhance organizational performance.
You can watch the overview video here
The Mobile Endpoint Agent is compatible with Android 11 and later. For system and firewall requirements, see the documentation.
Interactive Installation
Before you begin installation, generate and download the activation link or QR code from the ThousandEyes web UI (Endpoint Experience > Agent Settings > Add New Endpoint Agent). You’ll need the activation link or QR code during the agent installation process.
Locate the ThousandEyes Endpoint Agent application in the Google Play Store.
Install the application on your device.
Launch the application and click on Get Started.
During installation, scan the QR code or use the Activation Link provided to you to associate the agent with the appropriate ThousandEyes organization
Allow camera access to scan the QR code.
Grant the requested permissions :
Location Access (Allow all the time). Make sure Location Services are turned on in your device settings.
Background execution permission
Phone permission
Note: Screens may look different on devices running custom versions of Android or manufacturer-specific interfaces.
You will see the following screen upon successful installation and set-up of the agent.
MDM Installation
Cisco does not officially support or guarantee integration with third-party MDM technologies unless explicitly stated as part of a Cisco offer statement. If you are using a third-party MDM solution with Cisco products, you may encounter limitations in support from Cisco, particularly if the issue is due to a limitation, bug, or not supported by the MDM provider’s platform.
While Cisco ThousandEyes tests and validates that our applications support features such as silent deployment for Managed Google Play Apps, auto-granting permissions, automatic device naming, and parsing of connection strings, customers must seek direct support from their MDM provider for implementation and troubleshooting of these features. Cisco does not provide support for these functionalities when managed through third-party MDM platforms.
For the best experience, we recommend deploying the Mobile Endpoint Agent through Managed Google Play. This method supports managed configurations—so you can easily set permissions, device names, connection details, and enable auto-updates. Managed Google Play uses Google Play APIs to securely retrieve these settings from your MDM solution and apply them in MEPA, making management simple and efficient.
If you install the app by sideloading the APK or using Line of Business (LoB) deployment, managed configurations won’t be supported. This means you can’t automatically apply settings like permissions, device details, or connection information with these methods.
Getting Started
Generating Device Name Automatically
If your MDM system doesn’t provide a device name, the app creates one for you. The name is based on:
The first four letters of the device manufacturer’s name (with ‘X’ added if needed)
The first four letters of the device model name (with ‘X’ added if needed)
A randomly generated 16-character ID
For Example: Manufacturer: Google Model: Pixel 9 Generated device name: GOOGPIXE-3F4A7D9C1B2E5F60
Creating the App Configuration Schema
These configuration parameters are supported by the Mobile Endpoint Agent and should be configured through the MDM solution.
All supported MDM platforms follow Android Enterprise Managed Configurations and support UI or JSON inputs. You can configure it using the following schema:
UI Configuration Schema
connection_string
String
Unique id to register agent against an account group.
null
You can find this in the Thousandeyes web application (Endpoint Experience > Agent Settings > Add a New Endpoint Agent > Android > Connection String)
device_name
Variable
Name for the device
Auto-generated
Choose from one of these options for custom naming convention: free-form, Microsoft Entra Device ID, Account ID, IMEI, Intune Device IS, Mail, Partial UPN, User ID, User NAme, User Principal Name
skip_terms_of_service
Boolean
Flag used to auto grant terms of service, required for silent deployment.
False
True
JSON Configuration Schema (Example)
JSON
{
"kind": "androidenterprise#managedConfiguration",
"productId": "app:com.thousandeyes.endpointagent",
"managedProperty": [
{
"key": "skip_terms_of_service",
"valueBool": true
},
{
"key": "device_name",
"valueString": "{{SerialNumber}}"
},
{
"key": "connection_string",
"valueString": "abcd-1234-xyz-5678"
}
]
}
Application Permissions
ACCESS_BACKGROUND_LOCATION
Enables background location updates. It is needed for rough approximate geo-location data, along with Wi-Fi & Cellular metrics.
Auto-grant (fully managed devices)
READ_PHONE_STATE
Used to access network state or SIM info as well as cellular telemetry reporting.
Auto-grant (fully managed devices)
REQUEST_IGNORE_BATTERY_OPTIMIZATIONS
Required to keep running the app in the background.
Permission cannot be granted via MDM solution. Needs to be granted manually on the mobile device as a Background Execution permission.
SCHEDULE_EXACT_ALARM
Required to run scheduled periodic check-ins, tests and configuration.
Permission cannot be granted via MDM solution. Needs to be granted manually on the mobile device as a Background Execution permission.
You can install, configure, and deploy the agent on the following MDM platforms:
Cisco Meraki Systems Manager - Learn more about installing and managing the agent in this video. You may need to provide your business email address to request access.
Microsft Intune - Learn more about installing and managing the agent in this article.
Omnissa’s WorkspaceOne - Please refer to the manufacturer documentation on how to Deploy Public Apps and Android Profiles - Custom DPC Permissions.
SOTI
Verifying Agent Registration and Check-In
Sign in to the ThousandEyes application, and then go to the **Agent Settings **page under the Endpoint Experience menu.
Enter your device name as it appears in your mobile app. If you see your agent listed, registration was successful.
If the Last Contact column displays a recent timestamp, the agent has checked in.
Licensing
The Mobile Endpoint Agent supports both Advantage and Essential license types. Mobile devices can run up to four concurrent tests, regardless of the license type.
Configuring Tests
After you install and register your agent, you can configure tests to monitor your device’s performance.
Currently, only Network Tests and HTTP Server Tests are supported for scheduled tests. To set up a scheduled test, see the instructions for creating a custom test template.
Mobile agents can run up to four tests at the same time, with a minimum interval of five minutes between tests. Tests scheduled at shorter intervals will not run. Adjust your schedule or create separate tests for mobile agents as needed.
Managing the Endpoint Agents
In the Endpoint Experience > Agent Settings section of the ThousandEyes web app, you can verify, manage, and edit your agent settings.
You can also view agent details, such as created date, hostname, memory, OS version, manufacturer, and model. To see which tests are running on an agent, find the agent on the page, open its side panel, and review the allocated and running tests. To check that all assigned tests are active, hover over the Assigned Scheduled Tests graph. This process helps you quickly confirm agent configuration and test status.
To learn more about managing agent settings, see Manage Endpoint Agent Settings.
Viewing Data and Troubleshooting
Viewing Test Data
In the Endpoint Experience > Views section of the ThousandEyes web app, you can view test results associated with your agents.
Currently, only Scheduled Tests are supported. To see test data for all tests running on your agents, go to Endpoint Experience > Views > Scheduled Tests.
For detailed instructions on selecting tests, applying filters, and choosing metrics, see the Endpoint Agent Scheduled Tests article.
Troubleshooting for a Single Agent
The Agent Views section displays comprehensive endpoint data from an individual agent, delivering complete visibility to simplify troubleshooting and issue diagnosis, even for users with limited technical experience.
To access this feature, go to Endpoint Experience > Agent Views in the ThousandEyes web app and use the Search function to locate your desired agent.
To learn more about how to troubleshoot using the agent information, see Endpoint Agent Views.
Building Dashboards
Dashboards make it easy to monitor and visualize large volumes of test data, and help you quickly identify and resolve issues.
To help you track test results efficiently and reduce the need for external assistance, we offer Dashboard Templates. These templates promote consistency and support best practices for managing multiple account organizations.
Currently, you can use the following template to create dashboards for monitoring Mobile Endpoint Agents:
End User Localized Issues Dashboard
For more information about dashboards, see the following articles:
Setting Alert Rules
Alerting is a key feature of the ThousandEyes platform that notifies operations teams about performance issues or deviations. You can create alert rules for your critical monitoring scenarios, baseline and customize modular alert rules, and set up notifications and alert integrations. To learn more about alerts, see Alerts.
Zebra Support
We have thoroughly tested the product on a wide range of device types, including handheld, vehicle-mounted, wearable, and tablet devices. Based on our testing, we expect the solution to work with any Android 11 or later device that has access to Google Play. The certificate includes only base models; discontinued devices are not included.
System Requirements and Performance Disclaimer
The following metrics are based on internal testing conducted under controlled conditions. Results may vary depending on device model, OS version, background processes, and network conditions.
Test Environment:
Samsung Galaxy S21 Ultra - SM-G998U1 - Android 15
Memory (RAM): 16 GB
CPU: Octa-core (1x2.84 GHz Cortex-X1 & 3x2.42 GHz Cortex-A78 & 4x1.80 GHz Cortex-A55)
Battery: 5,000 mAh
Storage Used: Internal
During four concurrent monitoring tests over a 24-hour period, the following resource utilisation was recorded:
Battery Usage
1-3%
CPU Wake Events
420
Data Consumption
244 MB
Memory Footprint
53 MB
App Size
30 MB
These values represent typical usage under standard enterprise conditions. Actual performance and resource usage may vary. For optimal performance, devices should meet or exceed the listed specifications.
Limitations / Exceptions
Device Compatibility
Supported devices: Our solution is designed for Android 11 or later devices with access to the Google Play. Most Android phones and tablets include Google Play, but we recommend reviewing the complete list of Google Play-supported devices to confirm compatibility.
Hardware and software limitations: Some devices may have hardware or software restrictions that affect the installation or functionality of certain apps. Check app store availability for device-specific compatibility.
Synthetic Test Settings
Minimum test interval: The minimum test interval for mobile agents is 5 minutes. If an administrator tries to set a shorter interval, a warning appears.
Maximum number of concurrent tests: Mobile devices can run up to four concurrent tests, regardless of license type.
Web tests targeting HTTP (clear-text) destinations are not supported.
Unsupported Features
Zebra built-in scanner camera: QR code scanning is currently supported only with the device’s internal camera.
CPU metrics, TCP protocol for network tests, and Wireless Metrics (Retransmission Rate, Roaming Events & Channel Swap Events) are not supported on mobile devices.
Dynamic Tests, Real User Tests and TCP Connect are not supported at this time.
Mobile Metrics: API and alerts for mobile metrics are not currently supported.
Future releases will include support for ChromeOS and Honeywell scanners.
Last updated